This is Part 3 in a series of migrating SharePoint from SBS 2003 to SBS 2011. Series posts are:
Introduction – Overview
Part 1 – Caveats and Considerations
Part 2 – Preparation steps on v2
Part 3 – Upgrading v2 database to WSS v3
Part 4 – Attaching upgraded database to WSS v3
Part 5 – Check WSSv3 for migration to Foundation 2010
Part 6 – Move database to SBS 2011
Part 7 – Post migration steps and considerations
In this part we are going to attach the SharePoint v2 databases we copied across from SBS 2003 to the version of SQL that comes with a standard installation of Windows SharePoint Services v3 (WSS v3).
Part of the migration process of Companyweb from SBS 2003 to SBS 2011 involves migrating to WSS v3 (and eventually to SharePoint Foundation 2010). This means you will have to install WSS v3 somewhere as a staging server. I am not to concerned about this here, as long as you have it running with the default setup you will be able to follow along. However, if was me, I’d be using a Virtual Machine of some form as my staging server for WSS v3 but I am not going to cover any of that. I am going to assume that you already have WSS v3 running in a default installation somewhere.
We need to get the Companyweb databases we copied from SBS 2003 attached to the version of SQL on our WSS v3 server. By default, the WSS v3 databases are stored on the system partition (C: drive) of the server and no graphical management tools are installed. It is however possible to manipulate the databases using the command line but a free graphical management tool is available from:
It is strongly recommended that you install this application on your server to make working with the Microsoft SQL Server 2005 Express Embedded Edition (SSEE) easier.
Once the management studio has been installed on the server it can be accessed via Start | All Programs | SQL Server Management Studio Express.
Once the management studio is running you will need to connect to the Microsoft SQL Server 2005 Express Embedded Edition (SSEE). To do so use the following string in the server name field:
Once the management console has connected you should see an interface similar to that of other SQL 2005 server installations. The databases are located under the database folder.
By default the location of the Microsoft SQL Server 2005 Express Embedded Edition (SSEE) data on the WSS v3 server will be:
and this cannot be changed during the installation process. In many cases, as the data held in the databases grows it may cause problems because typically C: is the Windows system partition.
Unlike Microsoft SQL Server 2005 Express Edition the Embedded Edition does not have a limitation on the size of a database, while the non-embedded edition has a maximum database limit of 4GB.
Attaching databases using SQL 2005
Locate the Database folder under the Server name.
Right mouse click the Database folder and select Attach from menu that is displayed.
Press the Add button to locate the SharePoint v2 database that you previously copied.
Navigate to the location on the disk in which you saved the copy of the original SharePoint v2 database. Select the MDF file (here STS_SERVER_1.mdf) and press the OK button.
Check that all the information now displayed is correct and when complete press the OK button to continue.
SQL Server 2005 will now attach the database. You should see the word Executing displayed in the lower left of the screen during this process.
When the process is complete, if you now examine all the databases listed under the Databases folders you should see your SharePoint v2 database (in this case STS_VMSBS2003P_1). Note, that you will also see the WSS v3 database (in this case WSS_content) that was installed during the setup of WSS v3. If you have not already taken note of what the WSS v3 database is you should do it now for later reference.
The next post will cover how to connect this migrated databases to WSS v3.