SharePont 2003 - Move content database
I have been unable to use Backup Restore because the topology was unsupported. I have successfully moved the config database. Now I have backed up and restored the SQL database for the content db and am having trouble finding out how to attach the content database back in to sharepoint. I normally use SP2007 but am having trouble locating the attach content db stsadm command. It may even be possible through Central Admin. Anyone know how this is done?
October 15th, 2010 1:54pm
I have recreated the target database with: CREATE DATABASE [WSS_Content] COLLATE Latin1_General_CI_AS_KS_WS exec sp_dboption [WSS_Content], autoclose, false GO Then I run this: DECLARE @AdminVSAccount nvarchar(255) DECLARE @ContentVSAccount nvarchar(255) SET @ContentVSAccount = N'DOM\USER'; SET @AdminVSAccount = N'DOM\USER'; EXEC sp_grantlogin @ContentVSAccount; EXEC sp_grantlogin @AdminVSAccount; EXEC sp_changedbowner @AdminVSAccount; IF NOT EXISTS (SELECT * FROM sysusers WHERE name=@ContentVSAccount) EXEC sp_grantdbaccess @ContentVSAccount; EXEC sp_addrolemember 'db_owner', @ContentVSAccount; And get Msg 15063, Level 16, State 1, Line 1 The login already has an account under a different user name. Msg 15410, Level 11, State 1, Procedure sp_addrolemember, Line 75 User or role 'SMC\sa07-sps' does not exist in this database. My main problem is that in trying to attach the existing db I am getting this: Database 'WSS_Content' already exists. Choose a different database name. (Error code: 1801). Aaaatghhhhh!
October 15th, 2010 3:14pm
Okay, I deleted the database. I let SharePoint create a new database with the same name. I then restored my SQL backup over that database. I now get 404 BAD REQUEST. Am I going about this completely the wrong way? How can I fix this?
October 15th, 2010 3:45pm
Below are the steps to restore the content database 1. Detach the existing content database from the web application using CA 2. Stop the Windows SharePoint Timer services 3. Create a new SQL database and restore the content database backup 4. Attach the content database using CA or STSADM command (addcontentdb) 5. Start the Windows SharePoint Timer services 6. Restart the IIS Senthilrajan Kaliyaperumal
October 15th, 2010 4:15pm
Hi, im sorry I deleted my previous post but hadn't seen that it was 2003 since I only read "I normally use SP2007" but maybe this post can help you http://vspug.com/holliday/2007/06/19/restore-production-sharepoint-2003-databases-to-test-servers/ it seems as if you just have to specify an existing database name when creating a new content db just like in 2007.
October 15th, 2010 4:37pm
I have managed to fix the unsupported topology error. I am trying to restore my databases but am getting: Portal creation failed Microsoft.SharePoint.SPException: The configuration database shows that the virtual server has been extended already. To extend this virtual server, click "Extend and map to another virtual server" in the Provisioning Options section of the Extend Virtual Server page. Not sure how to remove the Extension!
October 15th, 2010 6:49pm
All finished now. What a real pain it was. The "Unsupported Tolology" was caused by Search not being checked in the System Admin pages. It had been turned off because Search was very slow on the box and even Microsoft hadn't been able to suggest a cause. I am quite annoyed at this - since when does disabling a service break the Topology? It's old technology so I'll chill out! I was then able to Restore the SQL databases through the interface. I went round in a few crcles as the "Already Extended" message kept stopping me dead. In the end, all I had to do was rename the site in IIS. The config database had remembered the site name. All done now. We want to move the Web as well and had originally planned to move it to a box with an existing MOSS 2007 App on it. We'll probably do an upgrade first if we can, we just don't know if the applications which consume it will still work after the upgrade. At least my Friday weasn't a late one!
October 18th, 2010 11:24am