Export (0) Print
Expand All

Deploy using DBA-created databases (Windows SharePoint Services)

Updated: June 30, 2008

Applies To: Windows SharePoint Services 3.0

 

Topic Last Modified: 2008-08-08

In this article:

This information applies to Microsoft Windows Server 2003. If you are in a Windows Server 2008 environment, the steps to install and configure Internet Information Services (IIS), the Microsoft .NET Framework version 3.0, and Windows SharePoint Services 3.0 are different. For more information, see Deploy a simple farm on the Windows Server 2008 operating system (Windows SharePoint Services).

In many IT environments, database administrators (DBAs) create and manage databases. Security policies and other policies in your organization might require that DBAs create the databases that Windows SharePoint Services 3.0 requires. This article discusses how DBAs can create these databases and farm administrators can configure them.

This article describes how to deploy Windows SharePoint Services 3.0 in an environment in which DBAs create and manage databases. The deployment includes all the required databases and one portal site. This article only applies to farms that use Microsoft SQL Server 2000 with the most recent service pack or Microsoft SQL Server 2005 database software.

Some procedures in this article use the Psconfig and Stsadm command-line tools. These tools are both located in the following folder: Program Files\Common Files\Microsoft Shared\web server extensions\12\BIN.

NoteNote:
This article does not cover using the Windows SharePoint Services 3.0 graphical user interface tools to create or configure databases. For information about creating and configuring databases by using the Windows SharePoint Services 3.0 graphical user interface tools, see Deploy in a simple server farm (Windows SharePoint Services).

By using the procedures in this article, DBAs and farm administrators create and configure the following databases and components in the following order:

  1. Configuration database (only one per farm).

  2. Content database for Central Administration (only one per farm).

  3. Central Administration Web application (only one per farm — created by Setup).

  4. Windows SharePoint Services search database (only one per farm).

  5. Web application content databases (optional). There is one content database for each Web application; extending a Web application does not require an additional content database.

  6. Web applications (optional).

    NoteNote:
    As part of the Web site and application pool creation process, a Web application is also created in Internet Information Services (IIS). Extending a Web application will create an additional Web site in IIS, but not an additional application pool.

Before you install and configure the databases, be sure that your database servers have the recommended hardware and software. For more information about these requirements, see Determine hardware and software requirements (Windows SharePoint Services).

If you are using SQL Server 2005 database software, the DBA must configure surface area settings so that local and remote connections use TCP/IP only. All of the databases required by Windows SharePoint Services 3.0 use the Latin1_General_CI_AS_KS_WS collation. All of the databases require that the Setup user account be assigned to them as the database owner (or dbo). For more information about the security requirements for these databases, see Plan for administrative and service accounts (Windows SharePoint Services).

The DBA needs to create SQL Server logins for the accounts that are used to access the databases for Windows SharePoint Services 3.0 and add them to roles. For more information about required accounts, including specific permissions and user rights required for these accounts, see Plan for administrative and service accounts (Windows SharePoint Services).

The following table describes the accounts that are used to access the databases for Windows SharePoint Services 3.0.

 

Account Purpose Requirements

SQL Server Service Account

This account is used as the service account for the following SQL Server services:

  • MSSQLSERVER

  • SQLSERVERAGENT

If you are not using the default instance, these services will be shown as:

  • MSSQL$InstanceName

  • SQLAgent$InstanceName

SQL Server prompts for this account during SQL Server Setup. You have two options:

  • Assign one of the built-in system accounts (Local System, Network Service, or Local Service) to the logon for the configurable SQL Server services. For more information about these accounts and security considerations, refer to the Setting Up Windows Service Accounts topic (http://go.microsoft.com/fwlink/?LinkId=121664&clcid=0x409) in the SQL Server documentation.

  • Assign a domain user account to the logon for the service. However, if you use this option you must take the additional steps required to configure Service Principal Names (SPNs) in Active Directory in order to support Kerberos authentication, which SQL Server uses.

Setup user account

The Setup user account is used to run the following:

  • Setup on each server

  • The SharePoint Products and Technologies Configuration Wizard

  • The PSConfig command-line tool

  • The Stsadm command-line tool

  • Domain user account

  • Member of the Administrators group on each server on which Setup is run

  • SQL Server login on the computer running SQL Server

  • Member of the following SQL Server security roles:

    • securityadmin fixed server role

    • dbcreator fixed server role

If you run Stsadm command-line tool commands that read from or write to a database, this account must be a member of the db_owner fixed database role for the database.

Server farm account/Database access account

The Server farm account is used to:

  • Act as the application pool identity for the SharePoint Central Administration application pool.

  • Run the Windows SharePoint Services Timer service.

  • Domain user account.

  • If the server farm is a child farm with Web applications that consume shared services from a larger farm, this account must be a member of the db_owner fixed database role on the configuration database of the larger farm.

Additional permissions are automatically granted for this account on Web servers and application servers that are joined to a server farm.

This account is automatically added as a SQL Server login on the computer running SQL Server and added to the following SQL Server security roles:

  • dbcreator fixed server role

  • securityadmin fixed server role

  • db_owner fixed database role for all databases in the server farm

NoteNote:
If you are using the least-privilege principle for added security, use a different account for each service, process, and application pool identity for each Web application.

Use the procedures in this section to create the required databases and give the appropriate accounts membership in the database security groups or roles.

The procedures require action by the DBA and the Setup user account. Each step is labeled [DBA] or [Setup] to indicate which role performs the action.

The farm only has one configuration database and one content database for Central Administration. The following procedure is performed once for each farm.

Create and configure the configuration database, the Central Administration content database, and the Central Administration Web application
  1. [DBA] Create the configuration database and the Central Administration content database using the LATIN1_General_CI_AS_KS_WS collation sequence and set the database owner (dbo) to be the Setup user account.

  2. [Setup] Run Setup on each of the server computers that run Windows SharePoint Services 3.0. You must run Setup on at least one of these computers by using the Web front end installation option.

  3. [Setup] On the computer on which you used the Web front end installation option, do not run the SharePoint Products and Technologies Configuration Wizard after Setup. Instead, open the command line, and then run the following command to configure the databases:

    Psconfig –cmd configdb –create –server <SQL Server Name> –database <SQL Database Name> –user <Domain Name\User Name> –password <password> –admincontentdatabase <SQL Admin Content Database Name>

    NoteNote:
    SQL Database Name is the configuration database. Domain Name\User Name is the server farm account. SQL Admin Content Database Name is the Central Administration content database.
  4. [Setup] After the command has completed, run the SharePoint Products and Technologies Configuration Wizard and complete the remainder of the configuration for your server. This creates the Central Administration Web application and performs other setup and configuration tasks.

The following procedure will only have to be performed once for the farm. The farm only has one Windows SharePoint Services search database.

Create and configure the Windows SharePoint Services search database and start the Windows SharePoint Services Search service.
  1. [DBA] Create a database for the Windows SharePoint Services Search database using the LATIN1_General_CI_AS_KS_WS collation sequence and set the database owner (dbo) to be the Setup user account.

  2. [Setup] Open the command line, and then run the following command to configure the database and start the Windows SharePoint Services Search service:

    stsadm -o spsearch -action start -farmserviceaccount <Domain Name\User Name> -farmservicepassword <password> -farmcontentaccessaccount <Domain Name\User Name> -farmcontentaccesspassword <password> -databaseserver <Server\Instance> -databasename <Database Name>

NoteNote:
farmserviceaccount is the server farm account. farmcontentaccessaccount is the Windows SharePoint Services Search service account. For databaseserver, if you are using the default instance of SQL Server, you only have to specify the name of the computer running SQL Server. The databasename is the Windows SharePoint Services Search database.

For information about how to perform this procedure using the Stsadm command-line tool, see Spsearch: Stsadm operation (Windows SharePoint Services).

The following procedure is performed once for each portal site in the farm.

Create and configure the portal site Web application and content database
  1. [DBA] Create the portal site Web application content database using the LATIN1_General_CI_AS_KS_WS collation sequence and set the database owner (dbo) to be the Setup user account.

  2. [DBA] Using SQL Server Management Studio, add the application pool process account to the Users group and the db_owner role for the Web application content database.

  3. [Setup] Open the command line, and then run the following command to create the Web application and configure the portal site Web application content database:

    stsadm.exe -o extendvs -url <URL> -donotcreatesite -exclusivelyusentlm -databaseserver <Database Server Name> -databasename <Database Name> -apidtype configurableid -description <IIS Web Site Name> -apidname <App Pool Name> -apidlogin <Domain Name\User Name> -apidpwd <password>

    NoteNote:
    url is the URL (in the form http://hostname:port) of the portal site Web application. databasename is the content database for the portal site Web application. description is the text name you give to the Web site in IIS. apidname is the text name that you give to the Web application pool in IIS. apidlogin is the identity for the application pool in IIS. This is the application pool process account.
    ImportantImportant:
    This command must be run on the same computer that is indicated in the url parameter. This is the same computer that will be running the portal site Web application. The host name and port combination must not describe a Web application that already exists or an error results and the Web application is not created.

For information about how to perform this procedure using the Stsadm command-line tool, see Extendvs: Stsadm operation (Windows SharePoint Services).

This topic is included in the following downloadable book for easier reading and printing:

See the full list of available books at Downloadable books for Windows SharePoint Services.

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