August 29, 2006 at 7:31 am
We are running SQL Server 2000 Standard Edition sp3a on a WIN2003 Server with CRM and Reporting Services installed all on the same box.
I now need to move the CRM and Report Server SQL Server Backends to another Database Server (We want a Two Server deployment Model)
What I have done so far is backup the two CRM Databases and the two Reporting Services Databases (and all associated User IDs) on the the Server containing the CRM and Reporting Services APPS AND the SQL Server Backend and Restored them to a new SQL Server Backend Server. After doing this we successfully pointed the CRM app to the New Databases on the 2nd Server.
Now I'm not sure what to do with the Reporting Services peice of it !!!!
I found an article on how to move a Reporting Services Database
http://support.microsoft.com/?kbid=842425
but it seems like some things are missing????
It say move a SQL Server 2000 Reporting Services Database to another computer and make Reporting Services point to that Database to do the following:
Backup the ReportServer and ReportServerTempDB databases on the Source Server
Restore the Databases to a SQL Server Instance running on another Computer
(I did both of these steps and I also recreated all logins associated with CRM and Reporting Services on the new SQL Server
Next the Article says to make Reporting Services repoint to the database on the new sql server, run the RSCONFIG command line Utility. Did this.
Now, I'm not sure what else I need to do. There are a bunch of scheduled jobs on the original SQL Server that did not move ie: MSCRM Identity Reseeding, MSCRM Index Reseeding, MSCRM Stored Procedure Priming
Do I need to move these Jobs? I'd like to uninstall the SQL Server on the CRM/Reporting Services Box at some point ....
Should I backup MSDB on the Original Instance and restore it to the new SQL Server Backend...............
Also, how can I verify that moving the Reporting Services Backend peice of it worked?
Can anyone offer any suggestions?????
September 1, 2006 at 8:00 am
This was removed by the editor as SPAM
October 13, 2006 at 12:42 pm
CRM part was easy, just use the deployment manager to repoint to the new Server. Reporting Services was more of a challenge
Take a look at this link...
http://msdn2.microsoft.com/en-us/library/ms162837.aspx
To move a SQL Server 2000 Reporting Services database to another computer and to make Reporting Services point to that database, follow these steps:
1. | Back up the Reporting Services database and the Reporting Services temporary database on the source computer. Note By default, the name of the Reporting Services database is ReportServer, and the name of the Reporting Services temporary database is ReportServerTempDB. |
2. | Restore the databases that you backed up in step 1 on the appropriate instance of SQL Server on the destination computer. |
3. | To make Reporting Services point to the database that you restored in step 2, run the following command at a command prompt on the computer that is configured as the report server: RSConfig -c -s Server name -d Reporting Services database name -a Sql|Windows -u User name -p User password |
_______________________________________________________________________
And check THIS out!!! we also had to make some registry changes because we were moving from a local sql server instance to a named instance on another Server.
http://blogs.msdn.com/ukcrm/archive/2006/08/17/704229.aspx
As for all of the scheduled jobs, I just used Enterprise Mangler to 'script' them out and then ran the scripts against the MSDB database on the new Instance and the jobs all run fine.
Hope this helps!
October 16, 2006 at 11:28 am
good work! thanks for the update and links. they will come in handy.
Thank-you,
David Russell
Any Cloud, Any Database, Oracle since 1982
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply