Export (0) Print
Expand All
ABS
AND
ASC
COS
DAY
DDB
EXP
FV
IF
INT
LEN
LN
LOG
MAX
Me
MID
MIN
MOD
NOT
IS
NPV
ODD
OR
PI
PMT
PV
SIN
SLN
SUM
SYD
T
TAN
VAR
Expand Minimize

Remote SQL Server Deployment

Archived content. No warranty is made as to technical accuracy. Content may contain URLs that were valid when originally published, but now link to sites or pages that no longer exist.

If you plan to host many Web sites (more than 1,000) using Microsoft , 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 management tools. Using SQL Server on its own server also allows your server to devote its processor, memory, and disk resources to providing pages and files. For more information about SQL Server and , see Windows SharePoint Services Architecture .

If you want to run SQL Server on a separate server from , you must take specific steps to configure both your Web server computer and your SQL Server computer before, during, and after installing . For example, to set up , you must run Setup from the command line, using the remotesql=yes property. This topic describes the steps needed to configure one server running 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 with Multiple Host Names Deployment .

Note: Using WMSDE may be more secure than using SQL Server, because WMSDE cannot be connected to remotely.

Before Installing

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

Preparing the Web Server Computer

Before you install and configure , you should check to make sure you meet the hardware and software requirements. The following sections help you review the requirements.

Hardware and Software Requirements

To be able to set up with remote SQL Server, you must meet the following criteria:

  • One computer running Microsoft (Standard, Enterprise, Datacenter, or Web Edition). Note that the hardware requirements for are the same as the installation requirements.

    • The computer must be configured as a Web server (running Internet Information Services (IIS) in IIS 6.0 worker process isolation mode) and must be running ASP.NET. For more information about installing and configuring IIS and ASP.NET, see the documentation.

    • The computer must be using the NTFS file system. Microsoft Windows includes a conversion utility (Convert.exe) that you can use to convert an existing file allocation table (FAT) volume to NTFS without losing data.

  • Another computer with SQL Server 2000 Service Pack 3 or later. You can use SQL Server 2000 Standard or Enterprise edition with . For more information about installing SQL Server, see the SQL Server 2000 documentation.

  • The client computers must be running Microsoft Internet Explorer 5.01 or later (best results with Microsoft Internet Explorer 5.5 or later) or Netscape Navigator 6.2 or later to use features.

For a complete list of hardware and software requirements, see Hardware and Software Requirements .

Configuring the Intranet Server as a Web Server

IIS is not enabled by default in . To make your front-end server into a Web server, you must enable IIS.

Enable IIS and configure it to use IIS 6.0 worker process isolation mode

  1. Click Start , point to All Programs , point to Administrative Tools , and then click Manage Your Server .

  2. On the Manage Your Server page, click Add or remove a role .

  3. In the Preliminary Steps pane, click Next .

  4. In the Server Role pane, click Application server (IIS, ASP.NET) , and then click Next .

  5. In the Web Application Server Options pane, accept the default of ASP.Net , and then click Next .

  6. In the Summary of Selections pane, click Next .

  7. Click Finish .

  8. Click Start , point to All Programs , point to Administrative Tools , and then click Internet Information Services (IIS) .

  9. In Internet Information Services manager, click the plus sign (+) next to the server name, and then right-click the Web Sites folder and select Properties .

  10. In the Properties dialog box, click the Service tab.

  11. In the Isolation mode section, clear the Run WWW service in IIS 5.0 isolation mode check box, and then click OK .

    Note: The Run WWW service in IIS 5.0 isolation mode check box is only selected if you have upgraded to IIS 6.0 on from IIS 5.0 on Windows 2000. New installations of IIS 6.0 use IIS 6.0 worker process isolation mode by default.

Preparing the SQL Server Computer

Besides configuring the connection from your Web server computer to the SQL Server computer, you must also configure your SQL Server installation to work with . For to be able to connect to your SQL Server database from the remote Web server computer, it is recommended that you configure the SQL Server database to use Windows authentication.

Enable Windows authentication for SQL Server

  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 .

  3. Click the plus sign (+) next to SQL Server Group .

  4. Right-click the SQL Server name, and then click Properties .

  5. In the Properties dialog box, click the Security tab.

  6. 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.

Running Setup

By default, when you install , the Setup program installs Microsoft SQL Server 2000 Desktop Engine (Windows) (WMSDE). To use with a remote SQL Server computer, you must install without installing WMSDE. To do so, you run the Setup program with the remotesql command-line option. For more information about the remotesql option and other Setup options, see Command-Line Options for Setupsts.exe . If you prefer, you can also install without WMSDE by running a quiet, command-line installation, rather than running the full Setup program. For more information about a quiet installation, see Performing a Quiet Installation .

Install without installing WMSDE

  1. Download STSV2.exe to your computer.

    You can download STSV2.exe from the Microsoft Web site.

  2. Run STSV2.exe to extract the installation files.

  3. When the installation starts, click Cancel .

  4. Click Start , and then click Run .

  5. In the Open box, type c:\folder\setupsts.exe remotesql=yes (where c:\folder is the path to the Setupsts.exe file on your local computer).

    For example, if you installed the US English version of STSV2.exe, then the folder is c:\program files\STS2Setup_1033.

  6. Click OK .

    The Setup program opens.

  7. 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 .

  8. On the Type of Installation page, click Server Farm , and then click Next .

  9. On the Summary page, verify that only will be installed, and then click Install .

  10. Setup runs and installs .

After Installation

After the Setup process is complete, you can configure your administrative virtual server (including specifying an application pool to use for the virtual server processes), connect to your SQL Server computer, and then provide your virtual servers with . You perform these steps by using the SharePoint Central Administration pages, which open automatically when Setup is complete.

Configure the administrative virtual server

  1. On the Configure Admin Virtual Server page, in the Application Pool section, select Create a new application pool .

    Note: You can also use an existing application pool, but any Web application that is using the same application pool can modify the databases. This is a potential security risk.

  2. Type the name to use for the new application pool, and then specify whether to use a predefined or configurable security account for the application pool.

    • If you selected Predefined , select the security account to use.

    • If you selected Configurable , type the user name and password to use.

    It is recommended that you use a domain account, so that the account has rights to both the front-end Web server and the back-end database server. The account you use must have rights to create databases in SQL Server. In other words, this account must be a member of the Security Administrators and Database Creators roles in SQL Server.

  3. Click OK .

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 in SQL Server Enterprise Manager. This is a one-time only change. Once you have granted database creation permissions to the account used by the administration virtual server, this account can create databases for any subsequent virtual servers.

Grant database creation rights in SQL Server

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.

  6. In the Server Role list, select the Security Administrators and Database Creators check boxes, and then click OK .

After you configure the administrative virtual server (and grant SQL Server rights to the new application pool account, if necessary), you must restart Internet Information Services (IIS) by typing iisreset on the command line. After IIS is reset, you can click the link on the Application Pool Changed page to continue configuring to work with your remote SQL Server computer.

Connect to the remote SQL Server computer

  1. On the Set Configuration Database Server page, in the Configuration Database section, enter the server name and database name to use.

  2. Under Database connection type , select Use Windows integrated authentication (more secure, recommended) .

  3. Click OK .

Extending a Virtual Server with

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 . When you extend a virtual server, is applied to a virtual server and a top-level Web site is created. To extend a virtual server, you use HTML Administration pages.

Note: 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 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.

  5. In the Site Owner section, in the Account name box, type the user name for the site owner (in the format DOMAIN\username if the username is part of a Windows domain group).

  6. In the E-mail address box, type the e-mail address that corresponds to the account.

  7. 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.

  8. If you want to specify a path for the URL, in the Custom URL path box, type the path to use.

  9. If you are using quotas, select a template in the Select a quota template box of the the Quota Settings section.

  10. In the Site Language section, select the language to use.

  11. 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 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 , see Configuring Self-Service Site Creation .

Was this page helpful?
(1500 characters remaining)
Thank you for your feedback
Show:
© 2014 Microsoft