Comments on: Move Sharepoint 2007 Content Database http://www.skatercoder.com/2007/04/10/move-sharepoint-2007-content-database/ angela chng - Ruby on Rails / PHP web developer & skater girl in Singapore Sat, 08 Jan 2011 06:53:08 +0000 hourly 1 http://wordpress.org/?v=3.0 By: Steven Oberholzer http://www.skatercoder.com/2007/04/10/move-sharepoint-2007-content-database/comment-page-1/#comment-377 Steven Oberholzer Wed, 19 Nov 2008 13:15:04 +0000 http://audioreload.com/roadburn/?p=3#comment-377 We sat with issues in our Production Environment and had to get a Development environment up that was identical to the Production environment. Identical because there were potentially issues with the database as people had gone into the database and made direct database changes, something which you should never do... Quick way to do it: 1. Take a backup of your production content db. 2. Take a backup of your dev content db. 2.1. Make sure that you get the GUID of the SiteID of the Sites table in the original content database. This is at this moment referenced by the Config database in the SiteMap (and potentially the Sites) table. 3. Restore the production db backup over the dev content db. 4. In SQL Enterprise Manager: 4.1. Get the GUID of the site record in the Sites table in the Content DB - the new content db that you've just restored. This will definitely differ from the GUID in the Config DB. 4.2. Update the Config DB's SiteMap (and maybe Sites) table where the ID is equal to the previous ID, to the new Site ID. 5. Perform an IISRESET. WARNING: 1. It is not wise to play around in the SQL Databases. 2. Be careful that you don't have references in lets say document libraries, to the Production document libraries, as you might inadvertently update or delete these documents. We sat with issues in our Production Environment and had to get a Development environment up that was identical to the Production environment. Identical because there were potentially issues with the database as people had gone into the database and made direct database changes, something which you should never do…

Quick way to do it:
1. Take a backup of your production content db.
2. Take a backup of your dev content db.
2.1. Make sure that you get the GUID of the SiteID of the Sites table in the original content database. This is at this moment referenced by the Config database in the SiteMap (and potentially the Sites) table.
3. Restore the production db backup over the dev content db.
4. In SQL Enterprise Manager:
4.1. Get the GUID of the site record in the Sites table in the Content DB – the new content db that you’ve just restored. This will definitely differ from the GUID in the Config DB.
4.2. Update the Config DB’s SiteMap (and maybe Sites) table where the ID is equal to the previous ID, to the new Site ID.
5. Perform an IISRESET.

WARNING:
1. It is not wise to play around in the SQL Databases.
2. Be careful that you don’t have references in lets say document libraries, to the Production document libraries, as you might inadvertently update or delete these documents.

]]>