Remote SQL Server Deployment

If you plan to host many Web sites using Microsoft Windows SharePoint Services, it is recommended that you use Microsoft SQL Server on a separate server from your Web server. Using SQL Server on its own server allows you to host all of your databases together and manage them with SQL Server Enterprise management tools. For example, SQL Server provides backup and restore, database management, and full text searching, which are not available in WMSDE. Using SQL Server on its own server also allows your Windows SharePoint Services server to devote its processor, memory, and disk resources to providing pages and files. For more information about SQL Server and Windows SharePoint Services, see Windows SharePoint Services Architecture.

To run SQL Server on a separate server from Windows SharePoint Services, you must take specific steps to configure both your Web server and your SQL Server. This topic describes the steps needed to configure one server running Windows SharePoint Services and one server running SQL Server 2000, Service Pack 3 or later, working together across a network connection. This topic does not cover setting up a server farm, with multiple front-end and back-end servers. For more information about setting up a server farm, see Server Farm Scalable Hosting Deployment.

Before Installing Windows SharePoint Services

Before you are ready to install Windows SharePoint Services, you must be sure that your Web server computer meets certain software and hardware requirements, and can connect to your SQL Server computer. You must also configure your SQL Server computer to be ready to host Windows SharePoint Services data.

Preparing the Web Server Computer

Before you install Microsoft Windows SharePoint Services on your front-end Web server (Web server: A computer that hosts Web pages and responds to requests from browsers. Also known as an HTTP server, a Web server stores files whose URLs begin with http://.), you must first ensure that the required hardware and software are installed, is running Internet Information Services (IIS) and ASP.NET, and is properly configured for Windows SharePoint Services. For detailed information about preparing your front-end Web servers, see Preparing Front-End Web Servers for Windows SharePoint Services.

Preparing the SQL Server Computer

You must configure your SQL Server installation to work with Windows SharePoint Services. For Windows SharePoint Services to be able to connect to your SQL Server database, it is recommended that you configure the SQL Server database to use Windows authentication.

To set up your SQL Server, you must perform the following steps.

  • Install either SQL Server 2000, Service Pack 3 or later or SQL Server 2005.

You can use the Standard or Enterprise editions of SQL Server 2000 or SQL Server 2005 with Windows SharePoint Services. Be sure to install the latest service pack for SQL Server. For more information about installing SQL Server, see the SQL Server 2000 or SQL Server 2005 documentation.

  • Set a secure password for your SQL Server administration account.

You must know both the administrator user account and password to be able to connect between Windows SharePoint Services on the front-end Web servers and SQL Server on the back-end server. It is recommended that you set a secure password for the administration account. If you are using Integrated Windows authentication (recommended), you should use a domain account with permissions to create databases in SQL Server. At a minimum you must grant the account Security Administrators and Database Creators roles. If you are using SQL Server authentication, this means that the "sa" account should have a secure password. For more information about setting the administrator user name and password, see the SQL Server 2000 or SQL Server 2005 documentation.

  • Configure the authentication method for connections between the Web servers and SQL Server.

For better security, it is recommended that you use Integrated Windows authentication, rather than SQL Server authentication, for connections between your front-end Web server and the back-end database server. Integrated Windows authentication uses a domain user account to control access to SQL Server, rather than storing credentials in the registry and passing them across the network as in SQL Server authentication.

The steps for configuring SQL Server differ between SQL Server 2000 or SQL Server 2005, as detailed in the following procedures.

Enable Windows authentication for SQL Server 2000
  1. On your SQL Server computer, click Start, point to All Programs, point to Microsoft SQL Server, and then click Enterprise Manager.

 Note   To use SQL Server Enterprise Manager, you must be a SQL Server database administrator.

  1. In Enterprise Manager, click the plus sign (+) next to Microsoft SQL Servers.
  2. Click the plus sign (+) next to SQL Server Group.
  3. Right-click the SQL Server name, and then click Properties.
  4. In the Properties dialog box, click the Security tab.
  5. Under Authentication, select Windows only, and then click OK.

 Note   You can also select SQL Server and Windows but it is recommended that you use Windows authentication to connect to your SQL Server database.

Proceed to Grant database creation rights in SQL Server 2000.

Enable Windows authentication for SQL Server 2005
  1. On your server computer, click Start, point to All Programs, point to Microsoft SQL Server 2005, and then click SQL Server Management Studio.
  2. On the Connect to Server screen, select the name of the local server from the Server name drop-down list.
  3. Select Windows Authentication from the Authentication drop-down list and then click Connect.
  4. In Object Explorer, right-click the server name and then click Properties.
  5. On the Server Properties - <Servername> screen, in the Select a page section, click Security.
  6. In the Server authentication section, select Windows Authentication mode, and then click OK.

Proceed to Grant database creation rights in SQL Server 2005.

Grant database creation rights in SQL Server 2000

If you are using a domain account that does not already have database creation rights in SQL Server, you can give the account this access in SQL Server Enterprise Manager. This is a one-time only change. After you have granted database creation permissions to the account used by the Windows SharePoint Services administration virtual server application pool, this account can create databases for any subsequent virtual servers.

 Note   To use SQL Server Enterprise Manager, you must be a SQL Server database administrator.

  1. On your SQL Server computer, click Start, point to All Programs, point to Microsoft SQL Server, and then click Enterprise Manager.
  2. In Enterprise Manager, click the plus sign (+) next to Microsoft SQL Servers, click the plus sign (+) next to SQL Server Group, and then click the plus sign (+) next to your SQL Server computer.
  3. Click the plus sign (+) next to Security, and then right-click Logins, and click New Login.
  4. In the Name box, type the account in the form DOMAIN\name.
  5. Click the Server Roles tab on the New Login pane.
  6. In the Server Role list, select the Security Administrators and Database Creators check boxes, and then click OK.

Proceed to Installing Windows SharePoint Services.

Grant database creation rights in SQL Server 2005

If you have used a domain account that does not already have database creation rights in SQL Server, you can give the account this access using SQL Server Management Studio. This is a one-time-only change. After you have granted database creation rights to the account used by the Windows SharePoint Services administration virtual server, this account can create databases for any subsequent virtual servers.

  1. On your server computer, click Start, point to All Programs, point to Microsoft SQL Server 2005, and then click SQL Server Management Studio.
  2. On the Connect to Server screen, select the name of the local server from the Server name drop-down list.
  3. Select Windows Authentication from the Authentication drop-down list and then click Connect.
  4. In Object Explorer, click the plus sign (+) next to Security.
  5. Right-click Logins, and then click New Login.
  6. In the Login – New screen, in the Login name box, type the account in the form of DOMAIN\accountname.
  7. In the Select a page section, click Server Roles.
  8. In the Server roles list, select the securityadmin and dbcreator check boxes, and then click OK.

Installing Windows SharePoint Services

After you have prepared the back-end database and front-end Web server, you can install Windows SharePoint Services on the front-end Web server. Note that you must install Windows SharePoint Services on each front-end Web server.

The installation steps vary, depending on whether you are installing Windows SharePoint Services on Windows Server 2003 R2 or a prior version of Windows 2003 Server.

Install Windows SharePoint Services on Windows 2003 R2

This section describes how to install Windows SharePoint Services on Windows 2003 R2 using SQL Server 2000 as the database server.

Install Windows SharePoint Services with SQL Server 2000
  1. Click Start, point to Control Panel, and then click Add or Remove Programs.
  2. Click Add/Remove Windows Components.
  3. In the Windows Components dialog box, scroll down and locate Windows SharePoint Services, select its check box, and then click Next to begin installation.
  4. When prompted, insert the Windows Server 2003 R2 CD 2 and browse to %drive%\cmpnents\r2\setupsts.exe, where %drive% is the drive letter of your CD drive.

 Note   You can optionally browse to a network location where Setupsts.exe is located.

  1. Click Open, and then click OK.
  2. When the Installation Screen appears, click Server Farm, and then click Next.
  3. On the Summary page, verify that only Windows SharePoint Services will be installed, and then click Install.

Setup runs and installs Windows SharePoint Services. When installation is complete, you browser opens the Configure Administrative Virtual Server page.

  1. Choose to either use an existing application pool or create a new application pool.
  2. Select either a predefined security account or a configurable security account.
  3. Choose either NTLM or Kerberos authentication in the Security configuration section.

 Note   Choosing Kerberos authentication will require additional steps if you are using a domain account. The account must be configured as a Service Principal Name (SPN). You must have domain administrator rights to configure a Service Principal Name (SPN). Refer to the Microsoft Knowledge Base article 832769: How to configure a Windows SharePoint Services virtual server to use Kerberos authentication for additional information.

  1. Click OK.
  2. When the Application Pool Changed page appears, click Start, and then click Run.
  3. Type iisreset, and then click OK.
  4. When the command completes, click OK.

The Set Configuration Database Server page appears.

  1. Type the NETBIOS name of the server running SQL Server 2000.
  2. Type the SQL Server database name or click the check box to use an existing configuration data base.
  3. Select the connection type to use either Integrated Windows or SQL authentication.
  4. Select the Active Directory Account Creation mode you want to use.

 Note   This mode cannot be changed at a later time without uninstalling and reinstalling Windows SharePoint Services. If you are installing Windows SharePoint Services on a domain controller, you cannot select Active Directory Account Creation mode.

  1. Click OK.

The Windows SharePoint Services Central Administration page appears.

  1. Minimize or close this page and click Finish.

Proceed to Extending a Virtual Server with Windows SharePoint Services.

Install Windows SharePoint Services on Windows 2003

This section describes how to install Windows SharePoint Services on Windows 2003 using SQL Server 2000 as the database server.

Install Windows SharePoint Services with SQL Server 2000
  1. Download STSV2.exe to your computer.

You can download STSV2.exe from the Microsoft Download Center.

  1. Run STSV2.exe to extract the installation files.
  2. When the Windows SharePoint Services installation starts, click Cancel.
  3. Click Start, and then click Run.
  4. In the Open box, type %drive%\folder\setupsts.exe remotesql=yes (where %drive% is the drive letter in which SP2 exists and folder is the path to the Setupsts.exe file on your local computer).

For example, if you downloaded the US English version of STSV2.exe to drive c, then the path is c:\program files\STS2Setup_1033.

  1. Click OK.

The Windows SharePoint Services Setup program opens.

  1. On the End-User License Agreement page, review the terms, and then select the I accept the terms in the License Agreement check box, and then click Next.
  2. On the Type of Installation page, click Server Farm, and then click Next.
  3. On the Summary page, verify that only Windows SharePoint Services will be installed, and then click Install.

Setup runs and installs Windows SharePoint Services. When installation is complete, you browser opens the Configure Administrative Virtual Server page.

  1. Choose to either use an existing application pool or create a new application pool.
  2. Select either a predefined security account or a configurable security account.
  3. Choose either NTLM or Kerberos authentication in the Security configuration section.

 Note   Choosing Kerberos authentication will require additional steps if you are using a domain account. The account must be configured as a Service Principal Name (SPN). You must have domain administrator rights to configure a Service Principal Name (SPN). Refer to the Microsoft Knowledge Base article 832769: How to configure a Windows SharePoint Services virtual server to use Kerberos authentication for additional information.

  1. Click OK.
  2. When the Application Pool Changed page appears, click Start, and then click Run.
  3. Type iisreset, and then click OK.
  4. When the command completes, click OK.

The Set Configuration Database Server page appears.

  1. Type the NETBIOS name of the server running SQL Server 2000.
  2. Type the SQL Server database name or click the check box to use an existing configuration data base.
  3. Select the connection type to use either Integrated Windows or SQL authentication.
  4. Select the Active Directory Account Creation mode you want to use.

 Note   This mode cannot be changed at a later time without uninstalling and reinstalling Windows SharePoint Services. If you are installing Windows SharePoint Services on a domain controller, you cannot select Active Directory Account Creation mode.

  1. Click OK.

The Windows SharePoint Services Central Administration page appears.

  1. Minimize or close this page and click Finish.

Proceed to Extending a Virtual Server with Windows SharePoint Services.

Extending a Virtual Server with Windows SharePoint Services

After you set up the connection to your SQL Server computer, you are ready to extend the virtual servers on your Web server computer with Windows SharePoint Services. When you extend a virtual server, Windows SharePoint Services is applied to a virtual server and a top-level Web site is created. To extend a virtual server, you use HTML Administration pages.

 Notes 

  • Depending on the configuration of your server, you might receive a security alert from Internet Explorer Enhanced Security Configuration (enabled by default) when you browse to the newly extended site. For more information, see Internet Explorer Enhanced Security and Windows SharePoint Services.
  • If you had a previous version of SharePoint Team Services or FrontPage Server Extensions, you will need to upgrade the virtual server rather than extend it. For more information, see Upgrade Considerations.
Extend a virtual server with Windows SharePoint Services and connect to a remote SQL Server computer
  1. On the SharePoint Central Administration page, click Extend or upgrade virtual server.
  2. On the Virtual Server List page, click the name of the virtual server to extend.
  3. On the Extend Virtual Server page, in the Provisioning Options section, select Extend and create a content database.
  4. In the Application Pool section, select either Use an existing application pool or Create a new application pool.

 Note   It is recommended that you create a new application pool for each virtual server, so that they run in separate processes. This application pool should use a domain account, but it does not need to have database creation rights in SQL Server — the administration virtual server account will create any databases required.

If you selected Use an existing application pool, select the application pool to use. If you selected Create a new application pool, enter the new application pool name, user name, and password to use.

  1. In the Site Owner section, in the Account name box, type the user name for the site owner (in the format DOMAIN\name, if the username is part of a Windows domain group).
  2. In the E-mail address box, type the e-mail address that corresponds to the account.
  3. In the Database Information section, select the Use default content database server check box, or type the database server name and database name to use for a new content database.
  4. In the Security Configuration section choose either NTLM or Kerberos authentication.

 Note   Using a domain user account might require additional steps to add a Service Principal Name (SPN) to the account. Information about adding a Service Principal Name (SPN) to a domain user account is available in Using Integrated Windows Authentication with Windows SharePoint Services and the Microsoft Knowledge base article 832769: How to configure a Windows SharePoint Services virtual server to use Kerberos authentication.

  1. If you want to specify a path for the URL, in the Custom URL path box, type the path to use.
  2. If you are using quotas, select a template in the Select a quota template box of the the Quota Settings section.
  3. In the Site Language section, select the language to use.
  4. Click OK.

After a few moments, the virtual server is extended and a confirmation page is displayed. You can open the home page for your new Windows SharePoint Services Web site in your browser by using a link on the confirmation page.

You can continue to extend other virtual servers or configure Self-Service Site Creation so users can create their own sites. For more information about allowing users to create their own Web sites based on Windows SharePoint Services, see Configuring Self-Service Site Creation.

 
 
Applies to:
Deployment Center 2003