|
 |
 |
 |
|
Microsoft Knowledge Base Article
This article contents is Microsoft Copyrighted material.
©2005-©2007 Microsoft Corporation. All rights reserved. Terms
of Use |
Trademarks
Article ID: 925190 - Last Review: May 14, 2007 - Revision: 1.2 How to move a WMSDE content database that resides on a Windows SharePoint Services 2.0 server to a Windows SharePoint Services 3.0 serverThis article describes how to move a Microsoft SQL Server 2000 Desktop Engine (Windows) (WMSDE) content database that resides on a Microsoft Windows SharePoint Services 2.0 (WSS) server to a Microsoft Windows SharePoint Services 3.0 (WSS 3.0) server. When you move the WSS database to the WSS 3.0 server, the WSS database is upgraded to WSS 3.0. This occurs when you attach a WSS 3.0 Web application. To move a WMSDE content database that resides on a WSS server to a WSS 3.0 server, follow these steps: - Use the Prescan.exe tool to scan the WMSDE content database on the WSS server.
Note You must run the Prescan.exe tool on the WSS database to prepare the database to be added to the WSS 3.0 Web application.
To use the Prescan.exe tool to scan the WSS database, follow these steps:- Use an account that has administrative permissions to log on to the WSS server.
- Copy the Prescan.exe tool on the WSS 3.0 server to a folder on the WSS server.
Note The Prescan.exe tool is located on the WSS 3.0 server in the following folder: Program Files\Common Files\Microsoft Shared\web server extensions\12\BIN - Click Start, click Run, type cmd, and then click OK.
- Locate the folder to which you copied the Prescan.exe tool.
- At the command prompt, type the following command to scan the database:
prescan /all
- Use the Osql command to connect to the WSS database. To do this, follow these steps:
- At the command prompt, type the following command, and then press ENTER:
Osql –S Servername\sharepoint -E
Note In this command, Servername is the name of the WSS server. - At the 1> prompt, type the following command, and then press ENTER:
EXEC sp_detach_db contentDB name Note In this command, contentDB name is the name of the content database. - At the 2> prompt, type Go, and then press ENTER.
Note You may receive a message that resembles the following:database is in use and cannot be detached - net pause mssql$sharepoint
- net continue mssql$sharepoint
- On the WSS 3.0 server, create the following folder structure under the Windows folder:
SYSMSI\SSEE\MSSQL.2005\MSSQL\Data - Copy all the .mdf and .ldf files that are located in the WSS database to following folder on the WSS server:
WINDOWS\SYSMSI\SSEE\MSSQL.2005\MSSQL\Data - Use an account that has administrative permissions to log on to the WSS 3.0 server.
- On the WSS 3.0 server, download and install the Microsoft SQL Server Native Client and the Sqlcmd utility. These tools are available in the latest feature pack for Microsoft SQL Server 2005.
For more information about the feature pack for Microsoft SQL Server 2005, visit the following Microsoft Web site: - On the WSS 3.0 server, run the following command at the command prompt:
sqlcmd -S \\.\pipe\mssql$microsoft##ssee\sql\query -E - At the 1> prompt, type the following command, and then press ENTER:
EXEC sp_attach_db @dbname = N'contentDB name', @filename1 = N'D:\WINDOWS\SYSMSI\SSEE\MSSQL.2005\MSSQL\Data\contentDB name_1.mdf', @filename2 = N'D:\WINDOWS\SYSMSI\SSEE\MSSQL.2005\MSSQL\Data \contentDB name_1_log.ldf’ Note In this command, contentDB name is the name of the content database. - At the
2> prompt, type Go, and then press ENTER:
-
On the WSS 3.0 server, create a Web application to attach to the database.
For more information about how to create a Web application in WSS 3.0 server, see the administrative documentation.
If you have already created a new Web application, you must use the Manage Content Databases page to remove the content database from the Web application. This lets you add the migrated database from the WSS server.
To do this follow these steps:- On the WSS 3.0 server, click Start, point to Administrative Tools, and then click SharePoint 3.0 Central Administration.
- On the Central Administration page, click Application Management.
- On the Application Management page, click Content Databases.
- On the Manage Content Databases page, click the Web application that you want.
- Click the name of the new database that was created when you created the Web application.
- On the Manage Content Database Settings page, click to select the Remove content database check box, and then click OK.
- Use the Stsadm.exe command-line tool to attach the WSS database to the Web application. Windows SharePoint Services does not support using the Manage Content Databases page to add a WSS database to a Web application. Therefore, you must use the Stsadm.exe command-line tool to add the Windows SharePoint 2.0 database to the Web application.
To do this, follow these steps:- At the command prompt, locate the following folder:
\Program Files\Common Files\Microsoft Shared\web server extensions\12\BIN - At the command prompt, type the following command for more information about how to use the Stsadm.exe command-line tool.
stsadm -help addcontentdb The following output is generated:stsadm.exe -o addcontentdb
-url url
-databasename <database name>
[-databaseserver <database server name>]
[-databaseuser <database username>]
[-databasepassword <database password>]
[-sitewarning <site warning count>]
[-sitemax <site max count>]
For more information about WSS 3.0, visit the following Microsoft Web site:
For more information about how to change the location of the Windows SharePoint Services database files, click the following article number to view the article in the Microsoft Knowledge Base:
843580Â
(http://kbalertz.com/Feedback.aspx?kbNumber=843580/
)
How to change the location of the Windows SharePoint Services database files
APPLIES TO- Microsoft Windows SharePoint Services 3.0
| kbhowto kbexpertiseinter KB925190 |
Community Feedback System
Very often, it takes hours to solve a problem. Very often, you've looked high
and low, and have tried a lot of solutions. When you finally found it, chances
are, it was because someone else helped you. Here's your chance to give back.
Use our community feedback tool to let others know what worked for you and what
didn't.
Please also understand that the community feedback system is not warranted to be
correct, it's simply a system that we've built to let people try and help each
other. If something in a feedback response doesn't make sense to you, or you're
not comfortable making changes that the feedback talks about (like registry
edits), please consult a professional.
Thank you for using kbAlertz.com Feedback System.
-- Scott Cate
|
|
 |
|
 |
|
|
|
| |