We migrated our Sharepoint 2003 environment to Sharepoint 2007in May and at the time did not have our SQL 2005 environment setup yet so we placed the databases on our SQL 2000 cluster. I am attempting to move all our sharepoint Sharepoint 2007 databases over to SQL 2005, I am wondering if you anyone hadinsight or experience with this process. I have in our dev environment copied all the databases between SQL 2000 and 2005 and tried a couple methods; One is to run the psconfig and remove the farm from the existing SQL2000 server and point to a copy of the config database on SQL2005 but that does not change the pointers in the database so al the content is still running on the SQL 2000 server. I tried creating a new farm and adding everything back in which includes rebuilding the web applications; 3rd party web parts; and other customization. Is there a better process for this. It seems like the method of creating a new farm is the only option I can find. I have found a few other postings that mention stadam o renameserver.

Did you go with any of the options in the end? I am currently looking to move my MOSS database from a 2000 SQL server to a 2005 SQL server. There seems to be a lot of information out there regarding the moving of the databases; however some of it is quite contradictory. I was thinking it may bepossible to backup the SQL DBs and then restore them to another server then re run the SharePoint configuration again to pickup the move or is this an over simplified view of the procedure? Joseph

We are also facing same scenario. Is there any solution?

Hi Aditya, Had to rebuild to whole MOSS front end and restore backups into the SQL server. It was a total nightmare. However have since discovered a piece of software by AvePoint which promises a lot when it comes to migrating servers. Currently doing a 30 trial of this software for backups and future server migrations. Joseph

Microsoft has released some great documentation on moving MOSS to a new SQL server:http://technet.microsoft.com/en-us/library/cc512725.aspx

Hi David,The microsoft document is incomplete.To change the DB server i followed the steps below 1) Attach the database to the new server andset user rights. 2) In the Moss Server use stsadm to rename server stsadm -o renameserver -newservername <newname> -oldservername <oldname> Upto this microsoft document describes.But you can not login in to theCA So you have to run this alsostsadm -o updatefarmcredentials -userlogin <domain\user> -password <password>RegardsXavier Ravi

Simply what you say is I have a MOSS 2007 and I need to change the DB Server Right?... Quite simple, done this few times when I was in UK and should be fairly easy (unless its really fishy): Take the backup of all related databases from 2000 SQL and restore them on the new SQL 2005 Server, and make sure you either make previous databases offline or detached. Re-run the MOSS Setup on the front end server and when asks, point the content database location give the new database (2005) server name where it will auto pick it up for you and then continue the setup and finalize. Upon completion test the SharePoint site and Admin site which should be working fine. --- Failing this we may need to follow the Disaster Recovery kind of a plan where I will speak on backup and restore stratergies that can be taken into account as this is somewhat similar to that. --- and Im very sure we do not need that much!Priyanga.Cmb.Lk

I found using sql aliases to be the easiest and least error prone approach:http://stsadm.blogspot.com/2008/06/moving-databases-easy-way.html

May I just change my new sql server's Computer Name tooriginal after moving All database..?Is it ok?

Guys I need some help on a similar issueMoving MOSS 2007 from one domain to another. All hardware is new, The old site needs to stay running just to remove some of the subsites and the new site needs to be on a different domain, different SQL and new hardware... Any suggestions

Move all databases to a different database server Prepare the new database server by using the Prepare the database servers procedure.Record which Web applications are associated with the SSP by performing the following steps: On the SharePoint Central Administration Web site, on the Application Management page, in the Office SharePoint Server Shared Services section, click Create or configure this farms shared services.Record the associated Web applications that are listed on the Manage This Farms Shared Services page. Back up an SSP by performing the following steps: On the drive on which SharePoint Products and Technologies is installed, change to the following directory: %COMMONPROGRAMFILES%\Microsoft shared\Web server extensions\12\Bin.If you do not already know which node you want to back up, type the following command: stsadm -o backup -showtree To back up an SSP, type the following command: stsadm -o backup -directory <UNC path> -backupmethod full -item <SSP name> where UNC path is the UNC path (\\server name\folder name) of the backup folder and where SSP name is the name of the SSP that you want to back up. All databases associated with the SSP will be automatically included in the backup. Repeat these steps for each SSP that you want to back up. Remove the SSP by performing the following steps: On the disk on which Microsoft SharePoint Products and Technologies is installed, change to the following directory: %COMMONPROGRAMFILES%\Microsoft shared\Web server extensions\12\Bin.To remove an SSP, type the following command, and then press ENTER: stsadm -o deletessp -title <SSP name> -deletedatabases -force where SSP name is the name of the SSP that you want to remove. To detach the SSP content database from the SharePoint farm, type the following command, and then press ENTER: stsadm -o -deletecontentdb -url <URL> -databasename <database name> where URL is the URL of the Web application from which the content database will be detached and database name is the name of the content database to be detached. Repeat steps b and c for each SSP. Delete the SSP content databases. Start SQL Server Management Studio and connect to the database server.In Object Explorer, expand Databases.Right-click an SSP content database, point to Tasks, and then click Delete.On the Delete Object page, check that the database you want to delete is highlighted, and then click OK.Perform steps c and d for each SSP content database. Stop the farm by performing the following steps: On the server that is running the Central Administration Web site, in the Services snap-in, stop the following services: Microsoft Single Sign-On serviceOffice Document Conversions Launcher serviceOffice Document Conversions Load Balancer serviceOffice SharePoint Server Search serviceWindows SharePoint Services Administration serviceWindows SharePoint Services Search serviceWindows SharePoint Services Timer serviceWindows SharePoint Services Tracing serviceWindows SharePoint Services VSS Writer service On the server that is running the Central Administration Web site, at the command prompt, type iisreset /stop.Repeat step 6 on each server in the farm. Back up the databases on the source database server. Start SQL Server Management Studio and connect to the database server.In Object Explorer, expand Databases.Right-click the configuration database (usually named SharePoint_Config), point to Tasks, and then click Back Up.In the Back Up Database dialog box, in the Source area, select the type of backup that you want to perform from the Backup type list. For more information about which backup type to use, see Overview of Recovery Models (http://go.microsoft.com/fwlink/?LinkId=114396&clcid=0x409) in the SQL Server 2005 Books Online.Click Database.In the Backup set area, in the Name text box, type a name or use the default.In the Description text box, type a description of the backup.Specify how long the backup should be kept, or use the default. When the backup set expires, the backup set can be overwritten by any subsequent backups that have the same name. By default, the setting for the backup set is 0 days so that it never expires.In the Destination section, specify a location to store the backup set, or use the default. 10. Click OK to back up the database. 11. Repeat steps c through j for the remaining databases in the farm. In Windows Explorer, locate the database backup (.bak) files that you want to move, and then copy or move them to the destination server Important: In some environments, this step must be performed by the database administrator. Move only the backup files to the destination database server. Do not move any databases or other files at this time. Restore databases on the destination database server. Start SQL Server Management Studio and connect to the database server.In Object Explorer, expand Databases.Right-click the database that you want to restore, point to Tasks, point to Restore, and then click Database.In the Restore Database dialog box, specify the destination and the source, and then select the backup set or sets that you want to restore. The default values for destination and source typically suit most recovery scenarios. In the Select a page pane, click Options.In the Restore options section, select only Overwrite the existing database. Unless your environment or policies require otherwise, do not select the other options in this section.In the Recovery state section: If you have included all the transaction logs that you must restore, select RESTORE WITH RECOVERY.If you must restore additional transaction logs, select RESTORE WITH NORECOVERY.The third option, RESTORE WITH STANDBY, is not used in this scenario. Click OK to complete the restore operation.Repeat steps c through h for each database that you are restoring. Use SQL Server to copy to the destination server the logons for all service accounts, including SQL Server logins, fixed server roles, fixed database roles, and permissions for the databases.Refer the farm to the new database server by creating a SQL Server connection alias. Start the SQL Server Native Client Network Utility (%SYSTEM%\cliconfg.exe).On the General tab, verify that TCP/IP is enabled.On the Alias tab, click Add. The Add Network Library Configuration dialog box appears. In the Server alias box, enter the name of the current instance of SQL Server.In the Network libraries area, click TCP/IP.In the Connection parameters area, in the Server name box, enter the new server name and instance to associate with the alias, and then click OK.Repeat steps a through f on all servers that connect to SQL Server. Start the new farm by performing the following steps: In the Services snap-in, start the following services: Microsoft Single Sign-On serviceOffice Document Conversions Launcher service (optional)Office Document Conversions Load Balancer service (optional) Office SharePoint Server Search serviceWindows SharePoint Services Administration serviceWindows SharePoint Services Search serviceWindows SharePoint Services Timer serviceWindows SharePoint Services Tracing serviceWindows SharePoint Services VSS Writer service (optional) At the command prompt, type iisreset /start. Repeat steps a and b on each server in the farm. Restore an SSP to the new location. To obtain the backup GUID for the specific backup that you want to restore, type the following command, and then press ENTER: stsadm -o backuphistory -directory <UNC path> where UNC path is the path to the shared folder that contains the backup. To restore a database, type the following command, and then press ENTER: stsadm -o restore -directory <UNC path> -restoremethod new -backupid <GUID from backuphistory> -newdatabaseserver <SQL Server instance> where UNC path is the UNC path of the backup shared folder, GUID from backuphistory is the GUID for the specific backup package that you want to restore, and SQL Server instance is the name of the SQL Server instance where the SSP databases should be restored. Repeat this step for each SSP that you want to move. Important: By default, the first SSP to be restored becomes the default. Perform this step if you want to assign a different SSP as the default. Configure a restored SSP to be the default SSP: On the SharePoint Central Administration Web site, on the Application Management page, in the Office SharePoint Server Shared Services section, click Create or configure this farms shared services.On the Manage This Farms Shared Services page, click Change Default SSP.On the Change Default Shared Services Provider page, select the SSP that you restored from the SSP Name list, and then click OK. and also http://social.technet.microsoft.com/Forums/en-US/sharepointadmin/thread/f6081c73-1ce0-4fd6-a715-f368c574b6e5 Deepesh Yevle MCTS

Move all databases to a different database server Prepare the new database server by using the Prepare the database servers procedure.Record which Web applications are associated with the SSP by performing the following steps: On the SharePoint Central Administration Web site, on the Application Management page, in the Office SharePoint Server Shared Services section, click Create or configure this farms shared services.Record the associated Web applications that are listed on the Manage This Farms Shared Services page. Back up an SSP by performing the following steps: On the drive on which SharePoint Products and Technologies is installed, change to the following directory: %COMMONPROGRAMFILES%\Microsoft shared\Web server extensions\12\Bin.If you do not already know which node you want to back up, type the following command: stsadm -o backup -showtree To back up an SSP, type the following command: stsadm -o backup -directory <UNC path> -backupmethod full -item <SSP name> where UNC path is the UNC path (\\server name\folder name) of the backup folder and where SSP name is the name of the SSP that you want to back up. All databases associated with the SSP will be automatically included in the backup. Repeat these steps for each SSP that you want to back up. Remove the SSP by performing the following steps: On the disk on which Microsoft SharePoint Products and Technologies is installed, change to the following directory: %COMMONPROGRAMFILES%\Microsoft shared\Web server extensions\12\Bin.To remove an SSP, type the following command, and then press ENTER: stsadm -o deletessp -title <SSP name> -deletedatabases -force where SSP name is the name of the SSP that you want to remove. To detach the SSP content database from the SharePoint farm, type the following command, and then press ENTER: stsadm -o -deletecontentdb -url <URL> -databasename <database name> where URL is the URL of the Web application from which the content database will be detached and database name is the name of the content database to be detached. Repeat steps b and c for each SSP. Delete the SSP content databases. Start SQL Server Management Studio and connect to the database server.In Object Explorer, expand Databases.Right-click an SSP content database, point to Tasks, and then click Delete.On the Delete Object page, check that the database you want to delete is highlighted, and then click OK.Perform steps c and d for each SSP content database. Stop the farm by performing the following steps: On the server that is running the Central Administration Web site, in the Services snap-in, stop the following services: Microsoft Single Sign-On serviceOffice Document Conversions Launcher serviceOffice Document Conversions Load Balancer serviceOffice SharePoint Server Search serviceWindows SharePoint Services Administration serviceWindows SharePoint Services Search serviceWindows SharePoint Services Timer serviceWindows SharePoint Services Tracing serviceWindows SharePoint Services VSS Writer service On the server that is running the Central Administration Web site, at the command prompt, type iisreset /stop.Repeat step 6 on each server in the farm. Back up the databases on the source database server. Start SQL Server Management Studio and connect to the database server.In Object Explorer, expand Databases.Right-click the configuration database (usually named SharePoint_Config), point to Tasks, and then click Back Up.In the Back Up Database dialog box, in the Source area, select the type of backup that you want to perform from the Backup type list. For more information about which backup type to use, see Overview of Recovery Models (http://go.microsoft.com/fwlink/?LinkId=114396&clcid=0x409) in the SQL Server 2005 Books Online.Click Database.In the Backup set area, in the Name text box, type a name or use the default.In the Description text box, type a description of the backup.Specify how long the backup should be kept, or use the default. When the backup set expires, the backup set can be overwritten by any subsequent backups that have the same name. By default, the setting for the backup set is 0 days so that it never expires.In the Destination section, specify a location to store the backup set, or use the default. 10. Click OK to back up the database. 11. Repeat steps c through j for the remaining databases in the farm. In Windows Explorer, locate the database backup (.bak) files that you want to move, and then copy or move them to the destination server Important: In some environments, this step must be performed by the database administrator. Move only the backup files to the destination database server. Do not move any databases or other files at this time. Restore databases on the destination database server. Start SQL Server Management Studio and connect to the database server.In Object Explorer, expand Databases.Right-click the database that you want to restore, point to Tasks, point to Restore, and then click Database.In the Restore Database dialog box, specify the destination and the source, and then select the backup set or sets that you want to restore. The default values for destination and source typically suit most recovery scenarios. In the Select a page pane, click Options.In the Restore options section, select only Overwrite the existing database. Unless your environment or policies require otherwise, do not select the other options in this section.In the Recovery state section: If you have included all the transaction logs that you must restore, select RESTORE WITH RECOVERY.If you must restore additional transaction logs, select RESTORE WITH NORECOVERY.The third option, RESTORE WITH STANDBY, is not used in this scenario. Click OK to complete the restore operation.Repeat steps c through h for each database that you are restoring. Use SQL Server to copy to the destination server the logons for all service accounts, including SQL Server logins, fixed server roles, fixed database roles, and permissions for the databases.Refer the farm to the new database server by creating a SQL Server connection alias. Start the SQL Server Native Client Network Utility (%SYSTEM%\cliconfg.exe).On the General tab, verify that TCP/IP is enabled.On the Alias tab, click Add. The Add Network Library Configuration dialog box appears. In the Server alias box, enter the name of the current instance of SQL Server.In the Network libraries area, click TCP/IP.In the Connection parameters area, in the Server name box, enter the new server name and instance to associate with the alias, and then click OK.Repeat steps a through f on all servers that connect to SQL Server. Start the new farm by performing the following steps: In the Services snap-in, start the following services: Microsoft Single Sign-On serviceOffice Document Conversions Launcher service (optional)Office Document Conversions Load Balancer service (optional) Office SharePoint Server Search serviceWindows SharePoint Services Administration serviceWindows SharePoint Services Search serviceWindows SharePoint Services Timer serviceWindows SharePoint Services Tracing serviceWindows SharePoint Services VSS Writer service (optional) At the command prompt, type iisreset /start. Repeat steps a and b on each server in the farm. Restore an SSP to the new location. To obtain the backup GUID for the specific backup that you want to restore, type the following command, and then press ENTER: stsadm -o backuphistory -directory <UNC path> where UNC path is the path to the shared folder that contains the backup. To restore a database, type the following command, and then press ENTER: stsadm -o restore -directory <UNC path> -restoremethod new -backupid <GUID from backuphistory> -newdatabaseserver <SQL Server instance> where UNC path is the UNC path of the backup shared folder, GUID from backuphistory is the GUID for the specific backup package that you want to restore, and SQL Server instance is the name of the SQL Server instance where the SSP databases should be restored. Repeat this step for each SSP that you want to move. Important: By default, the first SSP to be restored becomes the default. Perform this step if you want to assign a different SSP as the default. Configure a restored SSP to be the default SSP: On the SharePoint Central Administration Web site, on the Application Management page, in the Office SharePoint Server Shared Services section, click Create or configure this farms shared services.On the Manage This Farms Shared Services page, click Change Default SSP.On the Change Default Shared Services Provider page, select the SSP that you restored from the SSP Name list, and then click OK. and also http://social.technet.microsoft.com/Forums/en-US/sharepointadmin/thread/f6081c73-1ce0-4fd6-a715-f368c574b6e5 Deepesh Yevle MCTS

Move all databases to a different database server Prepare the new database server by using the Prepare the database servers procedure.Record which Web applications are associated with the SSP by performing the following steps: On the SharePoint Central Administration Web site, on the Application Management page, in the Office SharePoint Server Shared Services section, click Create or configure this farms shared services.Record the associated Web applications that are listed on the Manage This Farms Shared Services page. Back up an SSP by performing the following steps: On the drive on which SharePoint Products and Technologies is installed, change to the following directory: %COMMONPROGRAMFILES%\Microsoft shared\Web server extensions\12\Bin.If you do not already know which node you want to back up, type the following command: stsadm -o backup -showtree To back up an SSP, type the following command: stsadm -o backup -directory <UNC path> -backupmethod full -item <SSP name> where UNC path is the UNC path (\\server name\folder name) of the backup folder and where SSP name is the name of the SSP that you want to back up. All databases associated with the SSP will be automatically included in the backup. Repeat these steps for each SSP that you want to back up. Remove the SSP by performing the following steps: On the disk on which Microsoft SharePoint Products and Technologies is installed, change to the following directory: %COMMONPROGRAMFILES%\Microsoft shared\Web server extensions\12\Bin.To remove an SSP, type the following command, and then press ENTER: stsadm -o deletessp -title <SSP name> -deletedatabases -force where SSP name is the name of the SSP that you want to remove. To detach the SSP content database from the SharePoint farm, type the following command, and then press ENTER: stsadm -o -deletecontentdb -url <URL> -databasename <database name> where URL is the URL of the Web application from which the content database will be detached and database name is the name of the content database to be detached. Repeat steps b and c for each SSP. Delete the SSP content databases. Start SQL Server Management Studio and connect to the database server.In Object Explorer, expand Databases.Right-click an SSP content database, point to Tasks, and then click Delete.On the Delete Object page, check that the database you want to delete is highlighted, and then click OK.Perform steps c and d for each SSP content database. Stop the farm by performing the following steps: On the server that is running the Central Administration Web site, in the Services snap-in, stop the following services: Microsoft Single Sign-On serviceOffice Document Conversions Launcher serviceOffice Document Conversions Load Balancer serviceOffice SharePoint Server Search serviceWindows SharePoint Services Administration serviceWindows SharePoint Services Search serviceWindows SharePoint Services Timer serviceWindows SharePoint Services Tracing serviceWindows SharePoint Services VSS Writer service On the server that is running the Central Administration Web site, at the command prompt, type iisreset /stop.Repeat step 6 on each server in the farm. Back up the databases on the source database server. Start SQL Server Management Studio and connect to the database server.In Object Explorer, expand Databases.Right-click the configuration database (usually named SharePoint_Config), point to Tasks, and then click Back Up.In the Back Up Database dialog box, in the Source area, select the type of backup that you want to perform from the Backup type list. For more information about which backup type to use, see Overview of Recovery Models (http://go.microsoft.com/fwlink/?LinkId=114396&clcid=0x409) in the SQL Server 2005 Books Online.Click Database.In the Backup set area, in the Name text box, type a name or use the default.In the Description text box, type a description of the backup.Specify how long the backup should be kept, or use the default. When the backup set expires, the backup set can be overwritten by any subsequent backups that have the same name. By default, the setting for the backup set is 0 days so that it never expires.In the Destination section, specify a location to store the backup set, or use the default. 10. Click OK to back up the database. 11. Repeat steps c through j for the remaining databases in the farm. In Windows Explorer, locate the database backup (.bak) files that you want to move, and then copy or move them to the destination server Important: In some environments, this step must be performed by the database administrator. Move only the backup files to the destination database server. Do not move any databases or other files at this time. Restore databases on the destination database server. Start SQL Server Management Studio and connect to the database server.In Object Explorer, expand Databases.Right-click the database that you want to restore, point to Tasks, point to Restore, and then click Database.In the Restore Database dialog box, specify the destination and the source, and then select the backup set or sets that you want to restore. The default values for destination and source typically suit most recovery scenarios. In the Select a page pane, click Options.In the Restore options section, select only Overwrite the existing database. Unless your environment or policies require otherwise, do not select the other options in this section.In the Recovery state section: If you have included all the transaction logs that you must restore, select RESTORE WITH RECOVERY.If you must restore additional transaction logs, select RESTORE WITH NORECOVERY.The third option, RESTORE WITH STANDBY, is not used in this scenario. Click OK to complete the restore operation.Repeat steps c through h for each database that you are restoring. Use SQL Server to copy to the destination server the logons for all service accounts, including SQL Server logins, fixed server roles, fixed database roles, and permissions for the databases.Refer the farm to the new database server by creating a SQL Server connection alias. Start the SQL Server Native Client Network Utility (%SYSTEM%\cliconfg.exe).On the General tab, verify that TCP/IP is enabled.On the Alias tab, click Add. The Add Network Library Configuration dialog box appears. In the Server alias box, enter the name of the current instance of SQL Server.In the Network libraries area, click TCP/IP.In the Connection parameters area, in the Server name box, enter the new server name and instance to associate with the alias, and then click OK.Repeat steps a through f on all servers that connect to SQL Server. Start the new farm by performing the following steps: In the Services snap-in, start the following services: Microsoft Single Sign-On serviceOffice Document Conversions Launcher service (optional)Office Document Conversions Load Balancer service (optional) Office SharePoint Server Search serviceWindows SharePoint Services Administration serviceWindows SharePoint Services Search serviceWindows SharePoint Services Timer serviceWindows SharePoint Services Tracing serviceWindows SharePoint Services VSS Writer service (optional) At the command prompt, type iisreset /start. Repeat steps a and b on each server in the farm. Restore an SSP to the new location. To obtain the backup GUID for the specific backup that you want to restore, type the following command, and then press ENTER: stsadm -o backuphistory -directory <UNC path> where UNC path is the path to the shared folder that contains the backup. To restore a database, type the following command, and then press ENTER: stsadm -o restore -directory <UNC path> -restoremethod new -backupid <GUID from backuphistory> -newdatabaseserver <SQL Server instance> where UNC path is the UNC path of the backup shared folder, GUID from backuphistory is the GUID for the specific backup package that you want to restore, and SQL Server instance is the name of the SQL Server instance where the SSP databases should be restored. Repeat this step for each SSP that you want to move. Important: By default, the first SSP to be restored becomes the default. Perform this step if you want to assign a different SSP as the default. Configure a restored SSP to be the default SSP: On the SharePoint Central Administration Web site, on the Application Management page, in the Office SharePoint Server Shared Services section, click Create or configure this farms shared services.On the Manage This Farms Shared Services page, click Change Default SSP.On the Change Default Shared Services Provider page, select the SSP that you restored from the SSP Name list, and then click OK. Deepesh Yevle MCTS