In Windows SharePoint Services v3, the databases ( there are quite a few databases) cannot be installed in a drive other then %systemdrive%. Yeah! It is called the Windows Internal Database. To move this database, you need to do some cool acrobats on the server! If you are comfortable with the thought of moving the database using GUI, head over to this site. Wait! I will help you do this with getting into the SharePoint Central Administration. How cool is that? Of course my steps are based on the fantastic post by Ian Morrish.
I am going to draw some excerpts from Ian’s post so that you understand what needs to be done and what I have done.
If you don’t have another SQL Server 2005 product installed on the WSS server,
Download SQL Server 2005 Command Line Query Utility (x86)
Download SQL Server Native Client (x86)
Source page for other things SQL
I have placed the above files in C:WSSV3 (will be standard folder for everything WSSV3)
Ok, now lets get my script out to install
c:wssv3sqlncli.msi /qn (quite and no notifcation)
After installation, you will find the utility installed in the following location:
C:Program FilesMicrosoft SQL Server90Toolsbinn
The Windows Internal Database is located in %windir%sysmsisseeMSSQL.2005MSSQLData
Now another script
net stop MSSQL$microsoft##ssee
copy %windir%sysmsisseeMSSQL.2005MSSQLDataWSS_Content*.* c:SharePointv3Database*.*
net start MSSQL$microsoft##ssee
sqlcmd -S .pipemssql$microsoft##sseesqlquery -E -i c:s2.sql
Lets understand this script:
WSS 3.0 ships with a new Windows Internal Database based on SQL Server 2005.
You will see it as a running service called MSSQL$MICROSOFT##SSEE. The first line stops this.
Then copy database which incidentally is WSS_Content to C:SharePointV3Database.
Start the service.
Now this is interesting. I need to detach the database and then reattach. I have done this as above. s2.sql contains
EXEC sp_detach_db @dbname = ‘WSS_Content’
EXEC sp_attach_db @dbname = ‘WSS_Content’, @filename1 = ‘C:SharePointv3DatabaseWSS_Content.mdf’, @filename2 = ‘C:SharePointv3databasewss_content_log.ldf’
Now delete the database.
This solution works. It works. It works!!!
Next UP: Using Configuration Wizard without the wizard!