`

How to move the databases that are used by SharePoint Portal Server 2003 to a computer that is running SQL Server

 
阅读更多
How to move the databases that are used by SharePoint Portal Server 2003 to a computer that is running SQL Server

<script> function loadTOCNode(){} </script>Article ID
:
894164
Last Review
:
December 14, 2006
Revision
:
3.1
On This Page

<script type="text/javascript"> var sectionFilter = "type != 'notice' && type != 'securedata' && type != 'querywords'"; var tocArrow = "/library/images/support/kbgraphics/public/en-us/downarrow.gif"; var depthLimit = 10; var depth3Limit = 10; var depth4Limit = 5; var depth5Limit = 3; var tocEntryMinimum = 1; </script>SUMMARY

<script type="text/javascript"> loadTOCNode(1, 'summary'); </script>This step-by-step article describes how to move the databases that are used by Microsoft Office SharePoint Portal Server 2003 to a computer that is running Microsoft SQL Server. Use the procedure that is described in this article if you originally installed SharePoint Portal Server 2003 and SQL Server on the same computer, and you now want to use a remote computer that is running SQL Server for database storage. Alternatively, use the procedure that is described in this article if you originally installed SharePoint Server 2003 and SQL Server on separate computers, and you now want to use a different remote computer that is running SQL Server for database storage.

Before you can move the databases to a remote computer that is running SQL Server, you must back up SharePoint Portal Server 2003 data, delete the portal sites on the server farm, remove component assignments, and then disconnect the server from the configuration database. After you do this, you must create a new configuration database, specify server farm account settings, specify component assignments, and then restore the backup of SharePoint Portal Server 2003 data to the server.

INTRODUCTION

<script type="text/javascript"> loadTOCNode(1, 'summary'); </script>This step-by-step article describes how to move the databases that are used by SharePoint Portal Server 2003 to a computer that is running SQL Server. Use the procedure that is described in this article if one of the following conditions is true:

•
You originally installed SharePoint Portal Server 2003 and SQL Server on the same computer, and you now want to use a remote computer that is running SQL Server for database storage.
•
You originally installed SharePoint Portal Server 2003 and SQL Server on separate computers, and you now want to use a different remote computer that is running SQL Server for database storage.
Back up SharePoint Portal Server 2003 data

<script type="text/javascript"> loadTOCNode(2, 'summary'); </script>Use the SharePoint Portal Server Data Backup and Restore tool to back up SharePoint Portal Server 2003 data. To do this, follow these steps:

1.
Start the SharePoint Portal Server Data Backup and Restore tool.
2.
Click the Backup tab.
3.
In the Backup location and name box, specify the location where you want to store the backup files. Additionally, specify the file name to use as a prefix for the backup files.
4.
Expand Available components, and then click All server farm components. Verify that the Ready check box is displayed next to the items that you want to back up. Additionally, verify that the Ready check box is selected for each item that you want to back up.
5.
Click Backup.
6.
Click OK when you receive the message that states that the backup operation completed successfully.
7.
On the File menu, click Exit to quit the SharePoint Portal Server Data Backup and Restore tool.
8.
Take screen shots of the Define Managed Paths page. To find the Define Managed Paths page, follow these steps:
a.
In Windows SharePoint Central Administration, click Configure Virtual Servers.
b.
Click the first extended virtual server in the list, and then click Define Managed Paths.
Take screen shots of the Define Managed Paths page. Repeat this procedure for all extended virtual servers that are listed on the Configure Virtual Servers page. Make sure that you take screen shots of the Define Managed Paths page for all extended virtual servers. These screen shots will be used for reference when you re-create the managed paths after you restore the SharePoint Portal Server 2003 data.
9.
Make a backup of the web.config file so that you have a list of existing safe control entries and custom Web Parts before you continue.
Back up the databases in SQL Server 2000

<script type="text/javascript"> loadTOCNode(2, 'summary'); </script>Back up the following databases in SQL Server 2000:

•
PortalSiteName _PROF
•
PortalSiteName _SERV
•
PortalSiteName _SITE
•
The SharePoint Portal Server 2003 configuration database. By default, this database is named SPS_Config_db.
To do this, follow these steps:
1.
Create a new folder on the hard disk drive to store the databases that you back up.
2.
Start SQL Server Enterprise Manager.
3.
Expand Microsoft SQL Servers, expand the server group, expand the appropriate server, and then expand Databases.
4.
Right-click the database that you want to back up, point to All Tasks, and then click Backup Database.
5.
If a path is displayed in the Destination box, click the path, and then click Remove.
6.
Click Add. Click File name, and then specify the location of the folder that you created in step 1 and the file name of the backup file. Use a file name that is the same as the name of the database. For example, when you back up the PortalSiteName _PROF database, specify the file name as PortalSiteName _PROF.
7.
Click OK three times.
8.
Click OK when you receive the message that the backup operation completed successfully.
9.
Repeat step 4 to step 7 for each database.
Verify that the value in the PortalRecoveryBackup column of the PortalProperties table that is in the content database is not set to Null

<script type="text/javascript"> loadTOCNode(2, 'summary'); </script>Verify that the value in the PortalRecoveryBackup column of the PortalProperties table that is in the content database is not set to Null. If the value in the PortalRecoveryBackup column is set to Null, you cannot restore SharePoint Portal Server 2003 data from a backup. Make sure that the value is not set to Null before you follow the remaining steps in this article.

To verify that the value in the PortalRecoveryBackup column of the PortalProperties table that is in the content database is not set to Null, follow these steps:

1.
Start SQL Server Enterprise Manager.
2.
Expand Microsoft SQL Servers, expand the server group, expand the appropriate server, and then expand Databases.
3.
Expand the content database, and then click Tables.

Note The name of the content database typically ends in _SITE.
4.
Right-click PortalProperties, point to Open Table, and then click Return all rows.
5.
Verify that the value in the PortalRecoveryBackup column is not set to Null.

If the value in the PortalRecoveryBackup column is set to Null, use the SharePoint Portal Server Data Backup and Restore tool to create a backup of SharePoint Portal Server 2003 data. Then, repeat steps 1 through 5 to verify that the value in the PortalRecoveryBackup column is no longer set to Null. The value in the PortalRecoveryBackup column should be populated when you create a backup by using the SharePoint Portal Server Data Backup and Restore tool.
Delete the portal sites on the server farm

<script type="text/javascript"> loadTOCNode(2, 'summary'); </script>To delete the portal sites on the server farm, follow these steps:

1.
Start SharePoint Portal Server Central Administration.
2.
Under Portal Site and Virtual Server Configuration on the SharePoint Portal Server Central Administration for ServerName page, click List and manage portal sites.
3.
Click the arrow next to the portal site, and then click Delete Portal Sites.
4.
Make sure that the Delete all databases check box is cleared. If the Delete all databases check box is selected, click to clear the Delete all databases check box.
5.
Click OK.
6.
Repeat steps 2 through 5 for each portal site on the server farm.
7.
Click Go to SharePoint Portal Server central administration on the Delete Portal Site page.
Remove e-mail server settings

<script type="text/javascript"> loadTOCNode(2, 'summary'); </script>If you configured an e-mail server for SharePoint Portal Server 2003, remove the e-mail server settings. To do this, follow these steps:

1.
Under Server Configuration on the SharePoint Portal Server Central Administration for ServerName page, click Configure e-mail server settings.

Note To help you remember the settings on the Configure E-mail Server Settings page so that you can restore the settings later, take a screen shot of this page before you remove the settings. To do this, press ALT+PRINT SCREEN, start Microsoft WordPad or Microsoft Word, and then click Paste on the Edit menu. On the File menu, click Save, and then specify a file name and location where you want to save the file.
2.
Remove the Simple Mail Transfer Protocol (SMTP) server and e-mail settings, and then click OK.
Remove component assignments

<script type="text/javascript"> loadTOCNode(2, 'summary'); </script>To remove component assignments, follow these steps:

1.
Under Server Configuration on the SharePoint Portal Server Central Administration for ServerName page, click Configure server topology.
2.
At the bottom of the Configure Server Topology page, click Change Components.
3.
In the Component Assignment area, click to clear the check boxes for each component that is currently assigned to the server. For example, click to clear the Web check box, the Search check box, and the Index check box.
4.
In the Job Server Component area, click None in the Job server box, and then click OK.
5.
Click Close.
Disconnect the server from the configuration database

<script type="text/javascript"> loadTOCNode(2, 'summary'); </script>To disconnect the server from the configuration database, follow these steps:

1.
Under Server Configuration on the SharePoint Portal Server Central Administration for ServerName page, click Configure configuration database server.
2.
In the Database Connections area of the Specify Configuration Database Settings for ServerName page, click Disconnect from configuration database, and then click OK.

Note If you receive an error message when you try to disconnect from the configuration database, follow the steps in the You receive an error message when you try to disconnect from the configuration database section.
You receive an error message when you try to disconnect from the configuration database

<script type="text/javascript"> loadTOCNode(3, 'summary'); </script>In certain scenarios, you receive the following error message when you try to disconnect from the configuration database:

You cannot remove this server because some components are still active. Deactivate these components on the Configure server topology and component assignments page and then try again.
To resolve this issue, follow these steps:
1.
Click SharePoint Portal Server in the left pane, and then click Configure server topology under Server Configuration on the SharePoint Portal Server Central Administration for ServerName page.
2.
Under Database Server Settings, verify that the Global e-mail server entry and the Single sign-on credentials entry are not configured.
3.
Under Component Assignments, verify that no components are assigned to the server. Click Close.
4.
Repeat the steps in the Disconnect the server from the configuration database section to disconnect the server from the configuration database. Then, use one of the following methods:
•
If you can disconnect, follow the steps in the Configure server farm account settings section.
•
If you cannot disconnect, go to step 5.
5.
Specify the component settings database server and the content database server. To do this, follow these steps:
a.
Click SharePoint Portal Server in the left pane, and then click Configure server topology under Server Configuration on the SharePoint Portal Server Central Administration for ServerName page.
b.
Next to the Component settings database server entry under Database Server Settings, click the name of the server.
c.
Click Go to SharePoint Portal Server central administration on the Operation Successful page.
d.
Click to clear the Use same server as configuration database check box on the Specify Settings for Component Settings Database page, type the name of the new server in the Server name box, and then click OK.
e.
Under Server Configuration on the SharePoint Portal Server Central Administration for ServerName page, click Configure server topology.
f.
Next to the Content database server entry under Database Server Settings, click the name of the server.
g.
Click to clear the Use same server as configuration database check box on the Specify Content Database page, type the name of the new server in the Server name box, and then click OK.
h.
Click Go to SharePoint Portal Server central administration on the Operation Successful page.
i.
Repeat the steps in the Disconnect the server from the configuration database section to disconnect the server from the configuration database. Then, use one of the following methods:
•
If you can disconnect, follow the steps in the Specify the content access account and portal site application pool identity section.
•
If you cannot disconnect, go to step 6.
6.
Use SQL Server Enterprise Manager to detach the configuration database. To do this, follow these steps:
a.
Start SQL Server Enterprise Manager.
b.
Expand Microsoft SQL Servers, expand the server group, expand the appropriate server, and then expand Databases.
c.
Right-click the configuration database, point to All Tasks, and then click Detach Database.
d.
Click OK in the Detach Database - DatabaseName dialog box.

The database is detached and is copied to the Drive:/Program Files/Microsoft SQL Server/MSSQL/Data folder.
e.
Click OK when you receive the message that states that the operation completed successfully.
f.
Repeat the steps in the Disconnect the server from the configuration database section to disconnect the server from the configuration database.
Specify the content access account and the portal site application pool identity

<script type="text/javascript"> loadTOCNode(2, 'summary'); </script>To specify the content access account and the portal site application pool identity, follow these steps:

1.
Specify the default content access account. To do this, follow these steps:
a.
In the Default Content Access Account area of the Configure Server Farm Account Settings page, click to select the Specify account check box.
b.
In the User name (DOMAIN/user name) box , type the user account that you want to use as the default content access account. Type the user account in DomainName/UserName format. Specify the password in the Password box and in the Confirm Password box.
2.
Specify the portal site application pool identity. To do this, type the user name that you want to use as the portal site application pool identity in the User name (DOMAIN/user name) box in the Portal Site Application Pool Identity area. Type the user name in DomainName/UserName format. Specify the password in the Password box and in the Confirm Password box.
3.
Click OK.
Create the configuration database

<script type="text/javascript"> loadTOCNode(2, 'summary'); </script>To create the configuration database on the new database server, follow these steps:

1.
In the Database Connections area of the Specify Configuration Database settings for ServerName page, click Create configuration database.
2.
In the Configuration Database Server area, type the name of the remote computer that is running SQL Server in the Database server box.
3.
In the Configuration Database Name area, specify the name that you want to use for the configuration database, and then click OK.
Configure server farm account settings

<script type="text/javascript"> loadTOCNode(2, 'summary'); </script>To configure server farm account settings, follow these steps:

1.
In the Contact E-mail Address area of the Configure Server Farm Account Settings page, type your e-mail address.
2.
In the Proxy Server Settings area, verify that Do not connect by using a proxy server is selected. Then, click OK.
Specify component assignments

<script type="text/javascript"> loadTOCNode(2, 'summary'); </script>To specify component assignments, follow these steps:

1.
At the bottom of the Configure Server Topology page, click Change Components.
2.
On the Change Component Assignments page, follow these steps:
a.
In the Component Assignment area, click to select the check boxes that are next to the components that you want to assign to the server. For example, click to select the Web check box, the Search check box, and the Index check box.
b.
In the Job server box in the Job Server Component area, click the name of the server.
c.
Click OK, and then click Close.
3.
If you want to configure an e-mail server, click Configure e-mail server settings under Server Configuration on the SharePoint Portal Server Central Administration for ServerName page.
4.
On the Configure E-Mail Server Settings page, specify the SMTP server and e-mail addresses that you want to use. Then, click OK.
Restore SharePoint Portal Server 2003 data

<script type="text/javascript"> loadTOCNode(2, 'summary'); </script>To restore SharePoint Portal Server 2003 data from a backup, follow these steps:

1.
Start the SharePoint Portal Server Data Backup and Restore tool.
2.
Click the Restore tab.
3.
Click Browse next to the Manifest file box.
4.
Locate the folder that contains the backup files, click the .xml manifest file, and then click Open.
5.
Expand Available components, and then click All server farm components.
6.
Click the SITEDBS item, and then click Edit.

Note Do not click to select the Parameters needed check box.
7.
In the Portal recovery information dialog box, follow these steps:
a.
In the IIS virtual server and portal Url area, verify that the following conditions are true:
•
The Microsoft Internet Information Services (IIS) virtual server is set to Default Web Site.
•
The portal URL is set to the URL that you want. For example, the URL is set to http:// ServerName.
b.
In the Database information area, click the name of the database server. Then, specify the names that you want to use for the content database, the user profile database, and the services database.

Note The name of the content database typically ends in _SITE. The name of the user profile database typically ends in _PROF. The name of the services database typically ends in _SERV.
c.
Click OK.
8.
Verify that the Ready check box is displayed for the SITEDBS item, and then click to select the Ready check box.

Note When you move databases to a remote computer that is running SQL Server, you do not have to restore the index. However, if you want to restore the index, make sure that the Ready check box that is next to the INDEX item is selected.
9.
Click Restore.
10.
Click OK when you receive the message that states that the restore operation completed successfully.
11.
On the File menu, click Exit to quit the SharePoint Portal Server Data Backup and Restore tool.
12.
From Windows SharePoint Services Central Administration, click Configure Virtual Servers. For each extended site, click Define Managed Paths, and then re-create the managed paths by using the reference screen shots that you took during backup.
13.
Restore the backup of the web.config file to re-create safe control entries and custom Web Parts entries.
REFERENCES

<script type="text/javascript"> loadTOCNode(1, 'references'); </script>For more information about how to move an installation of SharePoint Portal Server 2003 that uses Microsoft SQL Server Desktop Engine 2000 (MSDE) to SQL Server, click the following article number to view the article in the Microsoft Knowledge Base:

837848 (http://support.microsoft.com/kb/837848/) How to move SharePoint Portal Server 2003 from MSDE to SQL Server
For more information about how to back up and restore SharePoint Portal Server 2003, see the "Backup and Restore" topic in the Microsoft Office SharePoint Portal Server 2003 Administrator's Guide. The Microsoft Office SharePoint Portal Server 2003 Administrator's Guide (Administrator's Help.chm) is located in the Docs folder in the root folder of the SharePoint Portal Server 2003 CD.
分享到：
| 【收集】Request.ServerVariables参数集介 ...
评论
发表评论

您还没有登录,请您登录后再发表评论

相关推荐

    Beginning T-SQL with Microsoft SQL Server 2005 and 2008

    The examples throughout this book use the following sample databases, which are available to download from Microsoft: the sample database for SQL Server 2005 is called AdventureWorks, and the sample ...

    Pro SQL Server Internals

    The book provides a solid road map for understanding the depth and power of the SQL Server database server and teaches how to get the most from the platform and keep your databases running at the ...

    Professional Microsoft SQL Server 2008 Administration

    This book is a professional book, meaning the authors assume that you know the basics about how to query a SQL Server and have some rudimentary concepts of SQL Server already. For example, this book ...

    Pro.SQL.Server.Internals

    The book provides a solid road map for understanding the depth and power of the SQL Server database server and teaches how to get the most from the platform and keep your databases running at the ...

    How to Cheat at Securing SQL Server 2005

    SQL Server is the perfect product for the How to Cheat series. It is an ambitious product that, for the average SysAdmin, will present a difficult migration path from earlier versions and a vexing ...

    Beginning Microsoft SQL Server 2008 Administrator

    ❑ The last six chapters (Chapters 14–19) are dedicated to introducing you to the SQL Server 2008 services, and features including the Common Language Runtime (CLR), SQL Server’s Business ...

    Introducing SQL Server(Apress,2015)

    You'll learn how databases work and how to use the T-SQL language by practicing on one of the most widely-used and powerful database engines in the corporate world: Microsoft SQL Server. Do you ...

    Beginning SQL Server for Developers(Apress,4ed,2014).

    Now in its fourth edition, the book is enhanced to cover the very latest developments in SQL Server, including the in-memory features that are introduced in SQL Server 2014. Within the book, there ...

    [SQL Server] Microsoft SQL Server 2012 技术内幕 (英文版)

    Led by a team of SQL Server experts, you’ll learn the skills you need to exploit key architectural features. Go behind the scenes to understand internal operations for creating, expanding, shrinking...

    微软内部资料-SQL性能优化3

    An intent lock indicates that SQL Server wants to acquire a shared (S) lock or exclusive (X) lock on some of the resources lower down in the hierarchy. For example, a shared intent lock placed at the ...

    The Language of SQL(Addison,2ed,2016)

    Many SQL texts attempt to serve as an encyclopedic reference on SQL syntax — an approach that is often counterproductive, because that information is readily available in online references published ...

    SQL Server for C# Developers Succinctly

    Developers of C# applications with a SQL Server database can learn to connect to a database using classic ADO.NET and look at different methods of developing databases using the Entity Framework....

    微软内部资料-SQL性能优化5

    In a nonclustered index, the leaf level contains each index key, plus a bookmark that tells SQL Server where to find the data row corresponding to the key in the index. A bookmark can take one of two ...

    SQL Server 2014 Development Essentials - Masood-Al-Farooq, Basit A. [SRG].pdf

    This chapter covers how to add data to a table using the INSERT statement, how to delete the data using the DELETE statement, and how to update existing data using the UPDATE statement. This chapter...

    Microsoft SQL Server 2012 Bible

    This detailed guide not only covers all the new features of SQL Server 2012, it also shows you step by step how to develop top-notch SQL Server databases and new data connections and keep your ...

    how-databases-work.pdf

    When it comes to relational databases, I can’t help thinking that something is missing. They’re used everywhere. There are many different databases: from the small and useful SQLite to the powerful ...

    SQL Server T-SQL Recipes(Apress,4ed,2015)

    SQL Server T-SQL Recipes is an example-based guide to the Transact-SQL language that is at the core of SQL Server. This edition has been lightly updated for SQL Server 2014 and provides ready-to-...

    Inside the SQL Server Query Optimizer(Benjamin Nevarez,2010)

    The SQL Server Query Optimizer is perceived by many to be a magic black box, transforming SQL queries into high performance execution plans in the blink of an eye through some unknowable process....

    sql server 2008 administration

    For experienced DBAs, the goal is to introduce you to the new features of SQL Server 2008 that will improve your administration routines. For new DBAs, or for those who administer databases on a part-...

Magicbox
Global site tag (gtag.js) - Google Analytics