Move SQL databases to different server

[Tony Murray]

Hi

Does any have some good guidelines on the steps required to move the SQL
databases associated with Project Server 2003 and WSS from an existing server
to a new server.

The current setup is:
Project Server 2003 & WSS (on dedicated server)
Databases on separate SQLSever 2000 SP3a server.

The new target database server will also be running SQL Server 2000.

Thanks.
Tony

 

[Aaron Tamblyn]

Hi Tony,
I went through this a few months ago and successfully moved the Project
Server and WSS databases. I don't have a documented procedure for you but
can offer the following advice (from memory).

Reference Material
============

The Project Server 2002 article http://support.microsoft.com/?kbid=833422
was useful but only for information on moving the Project Server database.

There is the following technet article on moving the WSS database
http://www.microsoft.com/technet/prodtechnol/windowsserver2003/technologies/sharepoint/movewsdb.mspx

Process Notes
=========

Prep:
- Complete this on a test box first if this is a production system

- If you are moving the databases off a single server that hosts Project
Server then be aware that you will need at least the Analysis Services data
objects installed on the front end box.

- Backup the Project Server and WSS content databases on the source box

- Set up the service accounts on the new database server.

Conducting the move:
- Restore the databases onto the destination box

- Recreate the MSProjectServerUser and the MSProjectUser SQL logins for the
ProjectServer database as detailed in the MS article I referred to above.

- Use the EditSite tool to change the database connection. You will enter
the next server name and passwords for the MSProjectServerUser and
MSProjectUser logins. This sets the database connection for Project Server
and Project Pro.

- I recreated the cubes (including reassigning security roles) but you could
move the existing cubes from the old server. Either way you will need to set
the cube connection in Project Server Admin.

- I then went into WSS Central Admin and recreated the Configuration
database pointing to the new server.

- I then added a content site connecting to the restored WSS content database.

- I then ran PSCom+ to recreate the COM components. (Only because there was
mention about this in the MS article I refer to above)

- Remove the databases off the old server.

Testing:
Complete the same testing you would do after an installation, including:
- Test connecting with Project Pro and creating and publishing a schedule
- Test creating a Portfolio Analyser view and then connect and access the
view with a test account that should be able to access the view.
- Test Risks, Issues and Documents to ensure WSS is operational


I hope this helps.

 

[Aaron Tamblyn]

There is the following KB article that details the procedure:
http://www.kbalertz.com/kb_905386.aspx

 

[Tony Murray]

That's great info, thanks Aaron

Tony

Hi Tony,
I went through this a few months ago and successfully moved the Project
Server and WSS databases. I don't have a documented procedure for you but
can offer the following advice (from memory).

Reference Material
============

The Project Server 2002 article http://support.microsoft.com/?kbid=833422
was useful but only for information on moving the Project Server database.

There is the following technet article on moving the WSS database
http://www.microsoft.com/technet/prodtechnol/windowsserver2003/technologies/sharepoint/movewsdb.mspx

Process Notes
=========

Prep:
- Complete this on a test box first if this is a production system

- If you are moving the databases off a single server that hosts Project
Server then be aware that you will need at least the Analysis Services
data
objects installed on the front end box.

- Backup the Project Server and WSS content databases on the source box

- Set up the service accounts on the new database server.

Conducting the move:
- Restore the databases onto the destination box

- Recreate the MSProjectServerUser and the MSProjectUser SQL logins for
the
ProjectServer database as detailed in the MS article I referred to above.

- Use the EditSite tool to change the database connection. You will enter
the next server name and passwords for the MSProjectServerUser and
MSProjectUser logins. This sets the database connection for Project
Server
and Project Pro.

- I recreated the cubes (including reassigning security roles) but you
could
move the existing cubes from the old server. Either way you will need to
set
the cube connection in Project Server Admin.

- I then went into WSS Central Admin and recreated the Configuration
database pointing to the new server.

- I then added a content site connecting to the restored WSS content
database.

- I then ran PSCom+ to recreate the COM components. (Only because there
was
mention about this in the MS article I refer to above)

- Remove the databases off the old server.

Testing:
Complete the same testing you would do after an installation, including:
- Test connecting with Project Pro and creating and publishing a schedule
- Test creating a Portfolio Analyser view and then connect and access the
view with a test account that should be able to access the view.
- Test Risks, Issues and Documents to ensure WSS is operational


I hope this helps.