Upgrading to SQL 2000


The default installation of SharePoint uses WMSDE as the data engine for the content and configuration databases. WMSDE runs locally on the server and limits the total size of SharePoint sites to 2 GB per content database. However, WMSDE does not limit performance, which is a change from previous versions of the data engine.

Upgrading from WMSDE to SQL 2000 (SP3a) on a shared server increases the capacity of SharePoint sites and simplifies maintenance since you can use SQL Server Enterprise Manager to configure automated back-ups and perform other tasks .

Upgrading the databases to a dedicated server running SQL 2000 can significantly improve performance as well as capacity, particularly for high-volume sites.

If you install SQL 2000 on a shared server after installing SharePoint, setup should upgrade the WSMDE server instance to use SQL 2000. To verify the data engine used by a server instance:

  1. Start SQL Server Enterprise Manager.

  2. Register the server instance. SharePoint names the instance machinename /SHAREPOINT by default.

  3. Select the server instance and choose Action Properties.

    1. Use SQL Enterprise Manager to copy the content and configuration databases from the WMSDE server instance to your SQL Server instance. SharePoint names its configuration database sts_config and content databases sts_ machinename_n .

    2. Use the SharePoint Central Administration site to set your configuration database to the new database you just copied .

    3. Use SharePoint Central Administration to add the content database you just copied and remove the old one.

    Those last two steps require a little more detail. To change the configuration database:

    1. Display the SharePoint Central Administration home page.

    2. Select Set configuration database server.

    3. Enter the new server name; select Connect to an existing configuration database and click OK. Since you didn't rename the database when you copied it, you can use the same database name .

    To change the content database for a virtual server:

    1. Display the SharePoint Central Administration home page.

    2. Choose Configure virtual server settings and select the virtual server to change.

    3. Select Manage content databases Add a content database.

    4. Click OK to add the database. If the operation succeeds, SharePoint returns you to the Manage Content Databases page.

    5. Click on the previous database (it appears above the one you just added).

    6. Select Remove content database and click OK.

    To upgrade to a dedicated database server, install the SQL Server client tools on the SharePoint server. This allows you to copy the databases from the current shared server to the dedicated server. Then follow the procedures above for moving the configuration and content databases to the dedicated server. When upgrading to Portal Server, it is a good idea to move the database to a dedicated SQL Server.



Essential SharePoint
Essential SharePoint 2007: A Practical Guide for Users, Administrators and Developers
ISBN: 0596514077
EAN: 2147483647
Year: 2005
Pages: 153
Authors: Jeff Webb

flylib.com © 2008-2017.
If you may any questions please contact us: flylib@qtcs.net