I wanted to get feedback on how to migrate the databases from a test
sql server to a production sql server in a MOSS 2007 environment.  Our
setup in this scenario is a single test SQL server and a single web
front-end server.   Based on the documentation I have read, you should
be able to use stsadm.exe -o setconfigdb to change the location of the
configuration database; however, I have tried using the stsadm.exe -o
setconfigdb with no success.  After running the stsadm.exe -o
setconfigdb and then rerunning the Sharepoint Products and Technology
Configuration Wizard, the Central Administration site always pointed
back to the test server rather than the production server.  I do not
get an error...in fact, the result of running the command is "Operation
Completed Successfully"...however, the site still points to the wrong
configuration database on the wrong server.

After much trial and error, the only way I have been able to
successfully move all the needed databases from a test to production
sql server and have the web applications/central administration
application on the front-end web server open correctly and point to
the correct sql server is by using the process written in the attached
document.  I have taken some information I found on this website
(http://blogs.msdn.com/priyo/archive/2006/09/15/755490.aspx) and
modified it to meet my needs. I wanted to get any thoughts on the
process I have listed below and to get feedback on the process for
using the stsadm.exe -o setconfigdb command.

Thank you!
Jennifer

Database Migration from Test to Production Servers
Database Backup and Restore
1.       In SQL Server Enterprise Manager, backup all Office
SharePoint Server 2007 related databases from the test database
server.

2.       On the front-end web server, disconnect MOSS from the farm
using the Sharepoint Products and Technologies Configuration Wizard.

3.       In SQL Server Enterprise Manager, restore all Office
SharePoint Server 2007 related databases except the configuration
database and the central administrator content database to the
production database server.

Central Administration Configuration (Front-End Web Server)
1.       On the front-end web server, run the Sharepoint Products and
Technologies Configuration Wizard.

a.       Do not connect to an existing server farm. Enter the database
and server name information for the production database server.

b.       After the configuration wizard has completed, do not create a
shared service provider or portal site.

2.       Create three web applications: the Shared Service Provider,
the My Site web application, and the portal site.

3.       Detach the content databases from the newly created web
applications by doing the following:

a.       From the Application Management page click the Content
Databases link under the SharePoint Web Application Management
section.

b.       Change the web application from the drop down list
appropriately.

c.       Select the content database and select Offline for the
Database Status and check the Remove Content Database.

d.       Click OK.

4.       Attach the restored site content databases for the newly
created web applications.

a.       From the Application Management page click Content Databases
under SharePoint Web Application Management section.

b.       Change the web application from the drop down list
appropriately.

c.       Click Add a content database.

d.       Enter the SQL Server name and the name of the restored
database.

e.       Click OK.

5.       Restore the Shared Service Provider.

a.       From the Application Management page click Create or
configure this farm's shared services.

b.       Click Restore SSP.

c.       Add the necessary configuration information for the Shared
Service Provider web application, My Site web application, Shared
Service Provider database name and search database name.

d.       Click OK.

e.       Set the restored Shared Service Provider as the default
Shared Service Provider for the farm.

f.         Start the search crawl from the Search Setting page in the
Shared Service Provider administrator console.

6.       Start the WSS search service.

7.       Start the MOSS search service and perform a crawl.