Avatar of Apexadmin
Apexadmin
 asked on

Sharepoint 2007 to Sharepoint 2010 with separate MSSQL server

I currently have a 2003 server with Sharepoint 2007 on it. The databases are also on it, SQL 2008 express. I also have two virtual machines. One has SQL 2008 enterprise on it. The other is ready for Sharepoint 2010 to be installed.

I would like to migrate the databases to the dedicated SQL server and also upgrade to Sharepoint 2010. I am fairly new to this and have not performed this before. Can anyone provide me the best way to perform these actions and in what order as to not break the flow of production?
ExchangeMicrosoft SharePointMicrosoft SQL Server 2008

Avatar of undefined
Last Comment
Apexadmin

8/22/2022 - Mon
ASKER CERTIFIED SOLUTION
SharePointGirl

Log in or sign up to see answer
Become an EE member today7-DAY FREE TRIAL
Members can start a 7-Day Free trial then enjoy unlimited access to the platform
Sign up - Free for 7 days
or
Learn why we charge membership fees
We get it - no one likes a content blocker. Take one extra minute and find out why we block content.
Not exactly the question you had in mind?
Sign up for an EE membership and get your own personalized solution. With an EE membership, you can ask unlimited troubleshooting, research, or opinion questions.
ask a question
SOLUTION
Greg Burns

Log in or sign up to see answer
Become an EE member today7-DAY FREE TRIAL
Members can start a 7-Day Free trial then enjoy unlimited access to the platform
Sign up - Free for 7 days
or
Learn why we charge membership fees
We get it - no one likes a content blocker. Take one extra minute and find out why we block content.
Not exactly the question you had in mind?
Sign up for an EE membership and get your own personalized solution. With an EE membership, you can ask unlimited troubleshooting, research, or opinion questions.
ask a question
Apexadmin

ASKER
First, thank you for the info. I am just getting my head through all this info. I am being very cautious about going through all this, we use sharepoint quite a bit and I don't want to break it. I haven't touched the old one yet. I installed SP 2010 on a new server and I am configuring it now.

I think my plan is to migrate the databases to the new SQL server first and see how that turns out before I attach the new SP to it and update it.

This article was in the article that was posted above http://technet.microsoft.com/en-us/library/ms345483(SQL.90).aspx

Is that the best way to do it or is that a bit dated?
Greg Burns

Your KB article is correct, and provides more detail for a detach/attach SQL migration than SharePointGirl's article.  The article is for SQL 2005 but it's essentially the same process in SQL 2008 and SQL 2008 R2.  

But I usually DON'T go for the detach/attach migration, because it's sort of a one-way trip.  You are actually moving and reusing the same database files, and as soon as you mount them in the new farm they undergo a schema upgrade, meaning you can't move them back if something fails.  This will of course impact your production farm  

You might want to use this method if you're planning to retire a physical machine and move all SQL components to a new server.  If this is your scenario, then I'd split it into two seperate tasks: moving the SQL instance; stabilizing; then doing the SharePoint migration.

But if you're JUST doing a SharePoint migration (and especially if you're just testing) I prefer to backup the content databases and restore them to another SQL instance (or to the same SQL instance using new names).
http://msdn.microsoft.com/en-us/library/ms187510.aspx

This way the old farm stays online while you play with the upgrade on the new farm.  Assuming, of course, that you have storage space for two copies of all your content databases.  

Apexadmin

ASKER
Thank you for all the help and info. I will plunge into this soon.
This is the best money I have ever spent. I cannot not tell you how many times these folks have saved my bacon. I learn so much from the contributors.
rwheeler23