asked on HELP!!! Still testing the migration process from WSS 3.0 to SharePoint Foundation 2010.
Hi, I am not sure if this is a problem, but here is the scenario.
I am migrating from WSS 3.0 (default install, meaning it is using SQL 2005 EE locally) on Server 2003 R2 x32 to SharePoint Foundation 2010 x64 on Server 2008 R2 with remote database SQL Server 2005 x64.
Server1: Server 2003 R2 x32 Standard Edition / WSS 3.0 default install (database content name is "WSS_Content.mdf")
Server2: Server 2008 R2 Standard Edition / SPF 2010 x64 / database content name is "SharePointFoundation2010.
My question/concern is when I perform a back up of the WSS_Content (WSS 3.0) database and move it over to the new server running SQL 2005 x64 SP4 and attach it, will it need to the same name as the current database that I named during the SPF2010 Farm installation setup (SharePointFoundation2010.
If not, would I just be better off, uninstalling SharePointFoundation2010 and reinstalling it and using the default configuration name (SharePoint_Config) like the old WSS 3.0 has for it's?
Or maybe a better way to describe my concern is under SPF 2010 Web Applications section, the following:
- SharePoint - 80
- SharePoint Central Administration v4
Well, the SharePoint - 80 usually points to the "SharePoint_Config", but the Server2 configuration I installed was customized, I guess, because the SharePoint - 80 is pointing to the "SharePointFoundation2010"
Hopefully I am making sense, because I am not sure if I understand it myself. LOL
Thanks in advance.
I am migrating from WSS 3.0 (default install, meaning it is using SQL 2005 EE locally) on Server 2003 R2 x32 to SharePoint Foundation 2010 x64 on Server 2008 R2 with remote database SQL Server 2005 x64.
Server1: Server 2003 R2 x32 Standard Edition / WSS 3.0 default install (database content name is "WSS_Content.mdf")
Server2: Server 2008 R2 Standard Edition / SPF 2010 x64 / database content name is "SharePointFoundation2010.
My question/concern is when I perform a back up of the WSS_Content (WSS 3.0) database and move it over to the new server running SQL 2005 x64 SP4 and attach it, will it need to the same name as the current database that I named during the SPF2010 Farm installation setup (SharePointFoundation2010.
If not, would I just be better off, uninstalling SharePointFoundation2010 and reinstalling it and using the default configuration name (SharePoint_Config) like the old WSS 3.0 has for it's?
Or maybe a better way to describe my concern is under SPF 2010 Web Applications section, the following:
- SharePoint - 80
- SharePoint Central Administration v4
Well, the SharePoint - 80 usually points to the "SharePoint_Config", but the Server2 configuration I installed was customized, I guess, because the SharePoint - 80 is pointing to the "SharePointFoundation2010"
Hopefully I am making sense, because I am not sure if I understand it myself. LOL
Thanks in advance.
Microsoft SQL Server 2005Microsoft SharePointWindows Server 2008
Last Comment
Justin Smith
SOLUTION
THIS SOLUTION ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
ASKER
OK, so how do I proceed in connecting the database (WSS_Content) from the WSS 3.0 server to the new server running SQL Server 2005 SP4 with SharePoint Foundation 2010?
Would I perform a restore from SQL Server 2005 SP4 on the new server overwriting the current database for SharePoint Foundation 2010?
Or another way?
Would I perform a restore from SQL Server 2005 SP4 on the new server overwriting the current database for SharePoint Foundation 2010?
Or another way?
ASKER CERTIFIED SOLUTION
THIS SOLUTION ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
ASKER
Yes, I created a general WSS_Content database with my Foundation installation. So, it contains nothing of importants at this time.
Thanks, I will try this and let you know how it turns out.
Thanks again.
Thanks, I will try this and let you know how it turns out.
Thanks again.
Just an FYI, if you ever need remote assistance, I'm available.
ASKER
Thanks. I appreciate that. One last thing, how do I attach the wss_content database to the SharePoint Foundation web application?
Do I have to use the command prompt with "stsadm -o addcontentdb" command?
Also, why did I need to delete the current wss_content database on Foundation & from SQL Server 2005 when deleting the current web application then create a wss_content_temp database when creating a new web application just to delete the wss_content_temp database?
Sorry, I just don't understand why.
Thanks.
Do I have to use the command prompt with "stsadm -o addcontentdb" command?
Also, why did I need to delete the current wss_content database on Foundation & from SQL Server 2005 when deleting the current web application then create a wss_content_temp database when creating a new web application just to delete the wss_content_temp database?
Sorry, I just don't understand why.
Thanks.
ASKER
OK, I am missing something, because I cannot attach the content database to SharePoint Foundation.
Here is what I am trying:
Within SharePoint Foundation 2010 Management Shell:
stsadm -o addcontentdb WSS_Content.mdf
But it comes back with a command line error. No other details, just an error.
What am I missing?
I have never attached a content database in SharePoint before. So, I am sure it is something I am doing wrong.
Thanks.
Here is what I am trying:
Within SharePoint Foundation 2010 Management Shell:
stsadm -o addcontentdb WSS_Content.mdf
But it comes back with a command line error. No other details, just an error.
What am I missing?
I have never attached a content database in SharePoint before. So, I am sure it is something I am doing wrong.
Thanks.
SOLUTION
THIS SOLUTION ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
ASKER
Oh, OK. Opps. I already deleted the dummy temp database and am now trying to attach/upgrade the real database. It is already in SQL Server 2005 x64, just need to get Foundation to see it.
Gotcha, makes more sense now.
I really appreciate all your help with this. I have been trying off and on for over a year to get this migration completed. It has been a high priority but then again other fires make it sit on the back burner for sometime. Now I have time to complete this project and feel that I am very very close to finalizing it.
Thank again.
Gotcha, makes more sense now.
I really appreciate all your help with this. I have been trying off and on for over a year to get this migration completed. It has been a high priority but then again other fires make it sit on the back burner for sometime. Now I have time to complete this project and feel that I am very very close to finalizing it.
Thank again.
ASKER
Awesome. The test migration worked like a charm. Now to proceed with the production migration.
Also, how should I proceed if I want to add a ssl cert to the sharepoint site?
Do I do that during the migration or after I have the migration completed successfully?
Thanks again.
Also, how should I proceed if I want to add a ssl cert to the sharepoint site?
Do I do that during the migration or after I have the migration completed successfully?
Thanks again.
ASKER
I am sorry, if I am getting on another topic and should start another question thread then I can do that too. I just trying to ironing this out and be done with this project.
Wait till afte the migration and after everything is up and running on the new platform.
ASKER
OK. Thanks. You have been a life saver.
LOL. Glad it worked out.
Configuration database name: "SharePoint_Config" is the default name, but I customized it during setup and called it "SharePointFoundation2010"