Timeline for Tutorial to move WSS 3.0 DBs from Windows Internal to SQL 2005 Instance
Current License: CC BY-SA 3.0
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jul 19, 2011 at 18:01 | vote | accept | tcv | ||
| Jul 18, 2011 at 14:01 | comment | added | tcv | @Jesus -- Thank you much for commenting here, too! Thanks for the link. I am having a production meeting this morning and will bring up the options. | |
| Jul 18, 2011 at 13:40 | comment | added | Jesus Shelby | Once its attached to SQL, you attach the DB's to the Web App. You are performing a DB attach upgrade at this point. technet.microsoft.com/en-us/library/cc263299.aspx | |
| Jul 17, 2011 at 14:11 | comment | added | tcv | Hmmm... In the second link re: upgrading from Express to full SQL, there are two follow-up questions: 1. Does the full SQL install need to be newer than 2005? (I have licenses for 05, but not any others). 2. Maybe this is something different about Express 2008, but in WSS 3, the database is on a different server address entirely. \\.\pipe\MSSQL$MICROSOFT##SSEE\sql\query vs. \\servername\Sharepoint. I don't see how the author accounted for Sharepoint looking for the DBs in the old location? | |
| Jul 17, 2011 at 13:56 | comment | added | tcv | I just checked and it looks like we have an Open License for Server 2008. Since this is an ESXi server, we could deploy a 2008 Server configuration with Sharepoint 2010 Essentials. Hmmmmmmm.... | |
| Jul 16, 2011 at 20:54 | comment | added | tcv | Thanks. My anxiety over the whole procedure leads me to this question: Is it more troublesome to upgrade or to stay in WSS 3 and move the DBs into SQL 05? Keep in mind that we're going to do all of this on one server. -- Oh, this might be a wrinkle. We're running Windows Server 2003. | |
| Jul 16, 2011 at 0:33 | history | answered | Tom Resing | CC BY-SA 3.0 |