MOSS Forum

Ask Question   UnAnswered
Home » Forum » MOSS       RSS Feeds

MOSS 2007 - Database Migration from a Test to PRoduction Environment

  Asked By: Helen    Date: Sep 28    Category: MOSS    Views: 7148

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
(blogs.msdn.com/.../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



3 Answers Found

Answer #1    Answered By: Amrita Durgude     Answered On: Sep 28

How about just migrating the content database  from one server to another? You
can do this by taking a backup of the database, copying the .BAK file to the
production server and then restoring it there. At this point, you can then go
to the CA page and add the additional content database.

Answer #2    Answered By: Maricela Conway     Answered On: Sep 28

What about the Shared Service Provider database, Shared Service Provider search
database, the WSS Search database, and the configuration database? Do those not
matter when you move from one sql server to another?


Answer #3    Answered By: Vinay Thakur     Answered On: Sep 28

If you don't mind recreate SSP, search and schedule crawling on the
new environment, then you could just copy content database  over to
the new environment.