Why cant I move to a new database?

Discussion:

(too old to reply)

Grant

2005-02-09 15:25:13 UTC

Hi,

I have SPS and SQL on 2 seperate machines and I would like to move the SQL
server databases to a different server. I cannot find any good information
on how to do this and the help file doesnt help at all.

Heres what I have done:

SQL:
- Backup up all relevant databases off SQL server and restored them on the
new SQL server.
- In the "SPS01_Config_db" database (that was created by default when I
first installed SPS) I have replaced all the old server names to the name of
the new SQL server.

Sharepoint site:
- On the "Central Administration" page I changed the "Set default content
database server" to the new SQl server with no problems.
- When I click "Set configuration database server" and try and change the
server name there I get the following error message:

----------------------
Unable to get global configuration data.

-----------------------

- When I navigate back to the Central Administration page and click on
"Configure virtual server" and then click the website and then on that page
click "Add a content database" and try to add a new database I get the
error:

-----------------------

Cannot drop. The data type is being used. (Error code: 15180).

-----------------------

Can anyone please help me with this? Is there a document somewhere that
describes how to simply move to a new SQL server?

I would appreciate any help on this,

Thanks,
Grant

bobbers

2005-02-23 19:05:04 UTC

Permalink

Grant,
I'm right there with you. no good documentation. we are going through the
same senerio now.
there is a pretty good document on the MSD2D site on migrating to new SQL
server.
One step that may have been forgotten is to disconnect from the old database
first.

http://msd2d.com/Content/Tip_viewitem_03.aspx?section=Sharepoint&id=7f55242d-89b2-4281-839a-179034637212
you may need to sign up on site to see the document.
good luck.

Post by Grant
Hi,
I have SPS and SQL on 2 seperate machines and I would like to move the SQL
server databases to a different server. I cannot find any good information
on how to do this and the help file doesnt help at all.
- Backup up all relevant databases off SQL server and restored them on the
new SQL server.
- In the "SPS01_Config_db" database (that was created by default when I
first installed SPS) I have replaced all the old server names to the name of
the new SQL server.
- On the "Central Administration" page I changed the "Set default content
database server" to the new SQl server with no problems.
- When I click "Set configuration database server" and try and change the
----------------------
Unable to get global configuration data.
-----------------------
- When I navigate back to the Central Administration page and click on
"Configure virtual server" and then click the website and then on that page
click "Add a content database" and try to add a new database I get the
-----------------------
Cannot drop. The data type is being used. (Error code: 15180).
-----------------------
Can anyone please help me with this? Is there a document somewhere that
describes how to simply move to a new SQL server?
I would appreciate any help on this,
Thanks,
Grant

Hollis D. Paul

2005-02-24 15:33:08 UTC

Permalink

Post by Grant
Can anyone please help me with this? Is there a document somewhere that
describes how to simply move to a new SQL server?

Take a look at these entries:

Using SPSBackup to migrate to new servers
http://msmvps.com/obts/archive/2005/01/07/30241.aspx

Moving site from test to production
http://msmvps.com/obts/archive/2005/02/23/36814.aspx

Hollis D. Paul [MVP - Outlook]
***@outhousebythesound.com
Mukilteo, WA USA

Ray Ranson

2005-03-21 18:45:04 UTC

Permalink

Yes, there's little documentation on reconfiguring your farm but the solution
is not as painful as it would seem. There are quite a few steps to do this
but you must be prepared to point all your existing virtual servers to the
newly configured SQL server once you are done. You are in a sense, rebuilding
your farm. This would be the case even if you are now using a single
standalone server to run your entire Sharepoint instance and just want to add
the additional SQL server.

First go to Central Admin and select you topology page and change the job
server to none. Stop your extended WSS sites and portals (Not central admin)
and Search on your web search servers, then remove / disconnect from the
configuration database. Restore all your databases to the new SQL server;
preferrably via Single File DB Attach or SP_Attach_db threough SQL Query
Analzer. (SQL Books online will have the syntax) I would attach the MDF and
LDF files respectively. Do not restore the config db. This MUST be created on
the initial connection to your new SQL server. On the topology page you can
now select create config database on the new SQL server\instance. Be sure to
check your administrative and app pool accounts have dbsvr access - create
rights on the SQL server. Now that your new Config DB is created, (on the
topo page) set your content db server and component settings to the check
mark for "use same server as config db server. After restarting you websites,
the remainder of the work will be through Central Admin / Virtual server
administration to repoint to the database names that the sites were
originally associated with on the old SQL server. Hopefully you named them
and did not use the autoname feature when extending the VS.

If you need the further steps. Please reply back to this thread and I may be
able to assist in short order