ealock
asked on
Move SharePoint 2007 ContentDB from SQL 2005 to SQL 2008 R2
I am in process of moving our SharePoint 2007 instance to another server, I have done this before while maintaining the same SQL server version without problem. In this instance I am trying to put the Content DB that currently exists on SQL2005 SP3 to a SQL 2008 R2 server. When I try to connect the Content DB from the 2008R2 SQL server it fails with event log entries referring to schema not matching and invalid/missing stored procedures.
I have read it is possible to use SQL 2008R2 with SP 2007 and am guessing that would work if I build a new content DB. Has anyone tried to tackle moving the content db as described.
How I migrated the Content DB was to backup the existing 2005 DB, create a new DB on 2008 R2 and restore/overwrite with the file from 2005.
I have read it is possible to use SQL 2008R2 with SP 2007 and am guessing that would work if I build a new content DB. Has anyone tried to tackle moving the content db as described.
How I migrated the Content DB was to backup the existing 2005 DB, create a new DB on 2008 R2 and restore/overwrite with the file from 2005.
ASKER
Yes I have looked at those, I am trying to do this first in a test environment to verify operation to minimize downtime, the MOSS server is a new build out of Windows 2008 R2 and x64 MOSS. I have done this successfully while maintain the same version of SQL (2005 SP3)
It seems to be a SQL issue with the schema and stored procedures in 2005 vs SQL 2008R2. I ran into the same issue years ago when going from 2000 to 2005 and it was all work on the SQL side that resolved it, unfortunately I didn't keep any notes.
It seems to be a SQL issue with the schema and stored procedures in 2005 vs SQL 2008R2. I ran into the same issue years ago when going from 2000 to 2005 and it was all work on the SQL side that resolved it, unfortunately I didn't keep any notes.
Try this and hopefully it will resolve it:
http://shipoint.com/2010/09/24/update-database-schema-on-sharepoint-server-and-sql-server-database/
http://shipoint.com/2010/09/24/update-database-schema-on-sharepoint-server-and-sql-server-database/
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Well I have it working although not a definitive answer on the actual resolution, I believe Vitor was on the correct trail with the upgrade of the database being required.
Steps to resolution I took to get this content database functional:
I could not get the content database to be accessible on the target SQL server, I tried all the suggestions without any luck
I built a test environment with servers running the same OS, SharePoint and SQL that I was trying to get to work in our production environment. Brought the content database backup into the test environment and it worked using the same steps I had been trying in production
I backed up the content database on the development SQL system and brought it over to production and restored to a new db
This is probably the key, the production system had an empty content database (no site collections), when I went via the GUI to add the content database brought over from production an error occurred stating the db had to be upgraded and that it needed to be done via stsadm -o addcontent db. The content db was added via the stsadm method successfully. The empty content db was then removed leaving only the added content db available to the :80 web application. It worked.
Apologies for not having a more precise explanation of the issue and resolution. Thanks to all who contributed
Steps to resolution I took to get this content database functional:
I could not get the content database to be accessible on the target SQL server, I tried all the suggestions without any luck
I built a test environment with servers running the same OS, SharePoint and SQL that I was trying to get to work in our production environment. Brought the content database backup into the test environment and it worked using the same steps I had been trying in production
I backed up the content database on the development SQL system and brought it over to production and restored to a new db
This is probably the key, the production system had an empty content database (no site collections), when I went via the GUI to add the content database brought over from production an error occurred stating the db had to be upgraded and that it needed to be done via stsadm -o addcontent db. The content db was added via the stsadm method successfully. The empty content db was then removed leaving only the added content db available to the :80 web application. It worked.
Apologies for not having a more precise explanation of the issue and resolution. Thanks to all who contributed
ASKER
While the article provided did not provide resolution I am convinced that the production SQL server needed to upgrade this database before it was uasable
https://technet.microsoft.com/en-gb/library/cc262792%28v=office.12%29.aspx
https://technet.microsoft.com/en-us/library/cc262370%28v=office.12%29.aspx