Database 'ReportServer' does not exist

Shouldn't reporting services setup create ReportServer database
automatically?
The setup fails at the very end with this message:
SQL Server failed to execute command for server configuration. The error
was: Database 'ReportServer' does not exist. Check sysdatabases. ...
Thanks,
-StanYes, Reporting Services install should create the ReportServer and
ReportServerTempDB databases, as well as the AdventureWorks2000 sample
database if you specified that feature to be installed. Be sure that you
have permissions to create the database. Also check the Reporting Services
install log, it may have more information about the error you are receiving.
Jonathan Kyle, MCSD
Microsoft WebData Support Engineer
This posting is provided "AS IS" with no warranties, and confers no rights.
--
| From: "Stan" <nospam@.yahoo.com>
| Subject: Database 'ReportServer' does not exist
| Date: Thu, 16 Sep 2004 16:24:41 -0400
| Lines: 13
| X-Priority: 3
| X-MSMail-Priority: Normal
| X-Newsreader: Microsoft Outlook Express 6.00.2800.1437
| X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1441
| Message-ID: <OC#5asCnEHA.1236@.TK2MSFTNGP09.phx.gbl>
| Newsgroups: microsoft.public.sqlserver.reportingsvcs
| NNTP-Posting-Host: 12.148.36.131
| Path: cpmsftngxa06.phx.gbl!TK2MSFTNGP08.phx.gbl!TK2MSFTNGP09.phx.gbl
| Xref: cpmsftngxa06.phx.gbl microsoft.public.sqlserver.reportingsvcs:29431
| X-Tomcat-NG: microsoft.public.sqlserver.reportingsvcs
|
| Shouldn't reporting services setup create ReportServer database
| automatically?
|
| The setup fails at the very end with this message:
|
| SQL Server failed to execute command for server configuration. The error
| was: Database 'ReportServer' does not exist. Check sysdatabases. ...
|
| Thanks,
|
| -Stan
|
|
||||I have seen this error if there is not default directory set for SQL server
to create databases in. You can check this via Enterprise manager go to the
properties on the server node.
--
-Daniel
This posting is provided "AS IS" with no warranties, and confers no rights.
"Jonathan Kyle [MSFT]" <jkyle@.online.microsoft.com> wrote in message
news:5Pan3rynEHA.4040@.cpmsftngxa06.phx.gbl...
> Yes, Reporting Services install should create the ReportServer and
> ReportServerTempDB databases, as well as the AdventureWorks2000 sample
> database if you specified that feature to be installed. Be sure that you
> have permissions to create the database. Also check the Reporting
Services
> install log, it may have more information about the error you are
receiving.
> Jonathan Kyle, MCSD
> Microsoft WebData Support Engineer
> This posting is provided "AS IS" with no warranties, and confers no
rights.
> --
> | From: "Stan" <nospam@.yahoo.com>
> | Subject: Database 'ReportServer' does not exist
> | Date: Thu, 16 Sep 2004 16:24:41 -0400
> | Lines: 13
> | X-Priority: 3
> | X-MSMail-Priority: Normal
> | X-Newsreader: Microsoft Outlook Express 6.00.2800.1437
> | X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1441
> | Message-ID: <OC#5asCnEHA.1236@.TK2MSFTNGP09.phx.gbl>
> | Newsgroups: microsoft.public.sqlserver.reportingsvcs
> | NNTP-Posting-Host: 12.148.36.131
> | Path: cpmsftngxa06.phx.gbl!TK2MSFTNGP08.phx.gbl!TK2MSFTNGP09.phx.gbl
> | Xref: cpmsftngxa06.phx.gbl
microsoft.public.sqlserver.reportingsvcs:29431
> | X-Tomcat-NG: microsoft.public.sqlserver.reportingsvcs
> |
> | Shouldn't reporting services setup create ReportServer database
> | automatically?
> |
> | The setup fails at the very end with this message:
> |
> | SQL Server failed to execute command for server configuration. The
error
> | was: Database 'ReportServer' does not exist. Check sysdatabases. ...
> |
> | Thanks,
> |
> | -Stan
> |
> |
> |
>|||Yes, I ran out of space on SQL Server C: driver and setup failed to create a
reporting database
Thanks!
"Daniel Reib [MSFT]" <danreib@.online.microsoft.com> wrote in message
news:%233TUfQ3nEHA.592@.TK2MSFTNGP11.phx.gbl...
> I have seen this error if there is not default directory set for SQL
server
> to create databases in. You can check this via Enterprise manager go to
the
> properties on the server node.
> --
> -Daniel
> This posting is provided "AS IS" with no warranties, and confers no
rights.
>
> "Jonathan Kyle [MSFT]" <jkyle@.online.microsoft.com> wrote in message
> news:5Pan3rynEHA.4040@.cpmsftngxa06.phx.gbl...
> > Yes, Reporting Services install should create the ReportServer and
> > ReportServerTempDB databases, as well as the AdventureWorks2000 sample
> > database if you specified that feature to be installed. Be sure that
you
> > have permissions to create the database. Also check the Reporting
> Services
> > install log, it may have more information about the error you are
> receiving.
> >
> > Jonathan Kyle, MCSD
> > Microsoft WebData Support Engineer
> >
> > This posting is provided "AS IS" with no warranties, and confers no
> rights.
> > --
> > | From: "Stan" <nospam@.yahoo.com>
> > | Subject: Database 'ReportServer' does not exist
> > | Date: Thu, 16 Sep 2004 16:24:41 -0400
> > | Lines: 13
> > | X-Priority: 3
> > | X-MSMail-Priority: Normal
> > | X-Newsreader: Microsoft Outlook Express 6.00.2800.1437
> > | X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1441
> > | Message-ID: <OC#5asCnEHA.1236@.TK2MSFTNGP09.phx.gbl>
> > | Newsgroups: microsoft.public.sqlserver.reportingsvcs
> > | NNTP-Posting-Host: 12.148.36.131
> > | Path: cpmsftngxa06.phx.gbl!TK2MSFTNGP08.phx.gbl!TK2MSFTNGP09.phx.gbl
> > | Xref: cpmsftngxa06.phx.gbl
> microsoft.public.sqlserver.reportingsvcs:29431
> > | X-Tomcat-NG: microsoft.public.sqlserver.reportingsvcs
> > |
> > | Shouldn't reporting services setup create ReportServer database
> > | automatically?
> > |
> > | The setup fails at the very end with this message:
> > |
> > | SQL Server failed to execute command for server configuration. The
> error
> > | was: Database 'ReportServer' does not exist. Check sysdatabases. ...
> > |
> > | Thanks,
> > |
> > | -Stan
> > |
> > |
> > |
> >
>

Database reporting time differently than system

Hiya,

I have a database on a SQL Server 2000 (sp3a) installation. For some reason it's reporting time that is 7 hours ahead of the system time.

The application is on one server the DB is on a shared production server. The app server and the DB server are reporting the same system time and are using a network time server. All the other db's on the shared production db server are reporting time correctly.

My questions:

Is there a T-SQL query to use to see what the time/timezone is for that database?
Is there a T-SQL query I can use to set the db time (not the system time)?
Anyone have any other suggestions as to what could be wrong?

Thanks in advance for any help!
'cheleIs this from a select getdate() query in QA or the output of some app or stored proc? If app or stored proc, check for date manipulation. SQL Server picks up its time from the serer clock, there is no separate SQL Server clock.


Unless it is using the getutcdate(), which is also derived from the system date / time / time zone setting.

<QUOTE>
GETUTCDATE

Returns the datetime value representing the current UTC time (Universal Time Coordinate or Greenwich Mean Time). The current UTC time is derived from the current local time and the time zone setting in the operating system of the computer on which SQL Server is running.

Syntax

GETUTCDATE()

</QUOTE>|||Thanks for the help.

It's a canned app. Epolicy by McAfee, to be precise. I guess I will go to them for tech support now that I know it's probably not something I did.

Database Replication SQL 2000

I have two SQL 2000 servers. I want to make the primary and one the
secondary. I want to databases to stay replicated. If the Primary goes down
the Secondary would be used while we fix the Primary. Once the the Primary
is fixed it would be brought back online and the Secondary would replicate
it's data to the Primary. Then they would be in sync again.
What are my options here? What is the recomended way to accomplish this?
Thanks,
Scott
Scott,
there are many threads (and opinions!) on this sort of thing over the last
few months. I would recommend looking at queued updating subscribers
provided you aren't using BLOB datatypes.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
|||Use Transaction Replication with updating Subscriber or use Log Shipping.

database replication / publication ?

Hi,
I'd like to keep an extra copy for database X on SQL server A to SQL server
B. The database X doesn't update very often during the day (but the computer
does have other jobs to run at tthe work hour). Both server A and B run SQL
server 2000 and on the same network. Currently the size of database X's MDF
and LDF are around 6 GB (3GB each). It would be nice to keep database X
always be in sync with its copy, but it is not a must. If the database
replication/publication takes a lot of CPU or is time comsuing, it is OK to
do it with a nightly job.
What is the good practice in the case? Thanks for sharing your thoughts.
Shawn,
for an extra copy of X on a standby server, and where latency is allowed,
I'd consider using Log Shipping. This article helps explain some of the key
differences: http://www.replicationanswers.com/Standby.asp
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)

database replication

Hi, newbie here.
I have an sql express database on my local machine (xp sp2) with many tables populated with plenty of data.
How can i duplicate/replicate this database?
Seems like it should be a straight forward thing, but i guess not.

Thanks!
-GarySQL Express can only subscribe to a replication, it can't publish I'm afraid.

Database replication

I'm new in the area of data replication.
I hope someone is willing to help me on this little thing I'm trying to accomplish.

Problem description
--
There is one central SQL Express database. And one (or more) SQL Express database(s) on remote locations. This approach of databases remote and central is mandatory due to some application features later-on.
The local database(s) on the remote location(s) will act as a sort of backup in case there is no network connection. Meaning that the data is stored locally at all times. And moved to the central database once the network connection is on.

Updates to the local database(s) should trigger a process where all data is moved to the central database if there is a network connection. So for now, it’s a one way stream: remote to central.
This approach gives us the option to delay the moves - if needed. For example, the daily data is kept local and moved to the central site over night. Which is a good thing to have if network resources are limited during office hours.

Solution
To make this happen, I was thinking allong the lines of using triggered stored procedures.
Where a local database update triggers a stored procedure that checks the network connection and performs the move to the central database.
If there is more than one record in the remote database, all records are moved to the central database. Also, an entry should be added to a log-file.
If the network connection is not there for whatever reason, an entry should be written in a log-file stating that there was no connection to the central database.

Options
-
Another way of solving this is using RMO-based publications and subscribers.
Where the database on the remote locations are publishers. And the central database are subscribers. However, according to Microsoft:
- SQL Express can only act as a subscriber.
- Data is copied. And not moved.
According to the SQL-BOL, the first limitation doesn’t exist when using programmatic, transactional replication.
However, the second needs to be solved as well. And in the examples of SQL-BOL, this is not mentioned. At least not that I’m aware of.

There are some advantages using RMO. For example deploying a new version of the application. Or deploying an updated database schema. Please let me know if this is proven to be really usefull. If so, this would be the preferred method – provided that the limitations mentioned earlier are solved. And if using this method, I would prefer stored procedures or Visual Basic for programming this.

Help wanted
--
Like I stated earlier, I’m a newbie on these replication matters.
So I really would like some help with this.
Who is willing to help with suggestions and examples?
Sofar, I’ve been able to:
- Install SQL Express with network connections enabled
- Running the Management Studio and create the data model I would like to use
- Add data manually and via an ODBC connection (using a system wide DSN).
- Run SQL select commands against the added data.
So the infrastructure is up and running….

Best regards,

Will Moonen

The major issue you face with your proposal is that you just can't do 'push' Replication with SQL Express.

So, you will be limited in approaches. Perhaps using stored procedures will work for you. I would suggest that you consider using a combination of Stored Procedures, SQLCmd.exe, and Windows scheduler; then schedule the stored procedures to run at a certain interval. In your proposal, you indicate that data will be 'pushed' up to the central server upon change, or stored locally if there is no connection, and then 'pushed' up on the next change. What if there isn't a 'next change' for quite some time -how would the local data be pushed to central?

|||

Many thanks for your feedback!

> The major issue you face with your proposal is that you just
> can't do 'push' Replication with SQL Express.

Agree - i.e. when you want to start things from the management studio.
But what about a 'push' by using the stored procedures? That is supported
according to the Books-On-Line.

> So, you will be limited in approaches. Perhaps using stored procedures will work for you.
> I would suggest that you consider using a combination of Stored Procedures, SQLCmd.exe,
> and Windows scheduler; then schedule the stored procedures to run at a certain interval.

Mmm, scheduling via Windows is an option. But only as a last resort.
There are to many things that can go wrong when using the Windows scheduler.

> In your proposal, you indicate that data will be 'pushed' up to the central server upon change,
> or stored locally if there is no connection, and then 'pushed' up on the next change.
> What if there isn't a 'next change' for quite some time -
> how would the local data be pushed to central?

The data model is rather small. It could hold the data for weeks.
There should be a push at least once per 24 hrs.
If not, the central site of the application will signal this.

Database Replication

Hi,
I'm learning Database Replication. what's the Database Replication for? what
applications use this feature? Please advice.
Hi
Have you read the section "Introducing Replication" in Books Online?
Hillary Cotter has a book on replication
http://www.nwsu.com/0974973602X.html which may help if you proceed along
this route.
John
"js" <js@.someone@.hotmail.com> wrote in message
news:OkY%233g0TFHA.228@.TK2MSFTNGP12.phx.gbl...
> Hi,
> I'm learning Database Replication. what's the Database Replication for?
> what applications use this feature? Please advice.
>
|||For having the same (or nearly the same) data in different places.
The most obvious example is a salesperson wanting to have a subset of the
the sales database on his laptop with the ability to make changes locally
and then have those changes get synchronized into the corporate database
when he re-connects to the LAN.
Also frequently used in Reporting Server situations, where the main
transactional database is too busy to serve up large queries for reports.
One way replication ships the data to a db that the reports are run off.
HTH,
Kevin Hill
President
3NF Consulting
www.3nf-inc.com/NewsGroups.htm
www.DallasDBAs.com/forum - new DB forum for Dallas/Ft. Worth area DBAs.
"js" <js@.someone@.hotmail.com> wrote in message
news:OkY%233g0TFHA.228@.TK2MSFTNGP12.phx.gbl...
> Hi,
> I'm learning Database Replication. what's the Database Replication for?
> what applications use this feature? Please advice.
>
|||Thanks all...
|||"Kevin3NF" wrote in message
> For having the same (or nearly the same) data in different places.
> The most obvious example is a salesperson wanting to have a subset of the
> the sales database on his laptop with the ability to make changes locally
> and then have those changes get synchronized into the corporate database
> when he re-connects to the LAN.
> Also frequently used in Reporting Server situations, where the main
> transactional database is too busy to serve up large queries for reports.
> One way replication ships the data to a db that the reports are run off.
>
Thanks Kevin, There are good sample, easy to understand.
How about Analysis Services? Can you please give me some samples too.
|||When the CEO wants to know how many widgets were sold in the NorthEast
district in Q4, 2004...he's going to open up Excel, connect to the Analysis
Services database and select those parameters. Very easy and he doesn't
have to know any programming.
Lots of work goes into making that AS database, form bringing the data in,
to getting it ready for the boss to start slicing and dicing.
I've never played in that area, so my knowledge is limited. I am pitching a
project that involves this, so ping me in early 2006...I should be much more
well-versed by then :-)
Kevin Hill
President
3NF Consulting
www.3nf-inc.com/NewsGroups.htm
www.DallasDBAs.com/forum - new DB forum for Dallas/Ft. Worth area DBAs.
"js" <js@.someone@.hotmail.com> wrote in message
news:uqiB5q1TFHA.3584@.TK2MSFTNGP14.phx.gbl...
> "Kevin3NF" wrote in message
> Thanks Kevin, There are good sample, easy to understand.
> How about Analysis Services? Can you please give me some samples too.
>
>
|||Thanks Kevin...