Welcome Sign in
Resources for IT Professionals
Click to Rate and Give Feedback
TechNet
TechNet Library
Deploy using DBA-created databases (Office SharePoint Server 2007 for Search)

Updated: 2007-06-14

About deploying by using DBA-created databases

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 required by Microsoft Office SharePoint Server 2007 for Search.

This article discusses how DBAs can create these databases and farm administrators configure them. This article describes how to deploy Office SharePoint Server 2007 for Search in an environment in which DBAs create and manage databases. The deployment includes all the required databases, one portal site, a Shared Services Administration Web site, My Sites, and one Shared Services Provider (SSP). 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 or Stsadm command-line tools. These tools are located in the following folder: Program Files\Common Files\Microsoft Shared\web server extensions\12\BIN.

NoteNote:

This article does not cover using the Office SharePoint Server 2007 for Search graphical user interface tools to create or configure databases. For information about creating and configuring databases by using the Office SharePoint Server 2007 for Search graphical user interface tools, see Deploy in a simple server farm (Office SharePoint Server 2007 for Search).

Using these procedures, the DBA will create databases and the farm administrator will perform other configuration actions in the following order:

  • The configuration database (only one per farm).

  • The content database for Central Administration (only one per farm).

  • Central Administration Web application (only one per farm, created by Setup).

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

  • Start the Office SharePoint Server Search service.

For each portal site:

  • Portal site Web application content database.

For the SSP:

  • A content database for the Shared Services Administration Web application (if the SSP is using its own Web application).

  • SSP Search database.

  • SSP Web application (created by Setup if the SSP is using its own Web application).

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.

Required database hardware and software

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 (Office SharePoint Server 2007 for Search).

There are also requirements specific to the database server, and, 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 Office SharePoint Server 2007 for Search 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 (dbo, or db_owner).

For more information about the security requirements for these databases, see Plan for administrative and service accounts (Office SharePoint Server for Search).

Required accounts

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

The following table describes the accounts that are used to access the databases for Office SharePoint Server 2007 for Search.

Login Notes

Setup user account

The account that is used to run Setup on each server computer and to run the SharePoint Products and Technologies Configuration Wizard, the Psconfig command-line tool, and the Stsadm command-line tool.

Server farm account

This account is also referred to as:

  • Database access account

This account is:

  • The application pool identity for the SharePoint Central Administration Web application.

  • The service account for the Windows SharePoint Services Timer (SPTimer) service.

Windows SharePoint Services Search service account

Used as the service account for the Windows SharePoint Services Search service.

Office SharePoint Server Search account

Used as the service account for the Office SharePoint Server Search service. There is only one instance of this service.

SSP service account

This account is used to run SSP-related timer jobs. This type of timer job does not run under the Server farm account but rather the SSP Service account. This account is also used as the application pool identity for the application pool associated with the virtual directory associated with the SSP.

Application pool process account

Used to access content databases associated with the Web applications. We recommend that you use a separate application pool account for each Web application. This provides an added layer of security.

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. The SSP will use two accounts, one for the SSP service account and one for the application pool identity for the Shared Services Administration Web application.

Create and configure the databases

Use the procedures in this section to create the required databases and give the accounts membership in the database Users security group and database 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 following procedure will only have to be performed once for the farm, on the server you want to run the Central Administration Web site. The farm only has one configuration database and one content database for Central Administration.

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 server computer in the farm. You must run Setup on at least one of these computers by using the Complete installation option.

NoteNote:

The rest of the farm servers will be configured after the procedures in the article are finished and the farm is established. You will run the SharePoint Products and Technologies Configuration Wizard on these servers by selecting the Yes, I want to connect to an existing server farm option, instead of by using the commands used in this procedure.

  1. [Setup] On the server on which you used the Complete 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 <SqlServerName> –database <SqlDatabaseName> –user <DomainName\UserName> –password <password> –admincontentdatabase <SqlAdminContentDatabaseName>

NoteNote:

<SqlDatabaseName> is the configuration database. -user is the server farm account. <SqlAdminContentDatabaseName> is the Central Administration content database.

  1. [Setup] After the command has completed, run the SharePoint Products and Technologies Configuration Wizard and complete the remainder of the configuration for the server. This creates the Central Administration Web application and performs other setup and configuration tasks.

  2. [DBA] After the SharePoint Products and Technologies Configuration Wizard has completed, perform the following actions for both the configuration database and the Central Administration content database:

    • Add the server farm account, Office SharePoint Server Search account, and the SSP service account to the Users group.

    • Add the server farm account, Office SharePoint Server Search account, and the SSP service account to the WSS_Content_Application_Pools role.

  3. [Setup] To confirm that the databases were created and correctly configured, verify that the home page of the Central Administration Web site can be accessed. However, do not configure anything by using Central Administration at this time. If the Central Administration page does not render, verify the accounts used in this procedure and ensure that they are properly assigned.

The following procedure will only have to be performed once for the farm. The farm has only 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 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 <DomainName\UserName> -farmservicepassword <password> -farmcontentaccessaccount <DomainName\UserName> -farmcontentaccesspassword <password> -databaseserver <server\instance> -databasename <DatabaseName>

    Note   -farmserviceaccount is the server farm account. -farmcontentaccessaccount is the Office 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 following procedure must be performed once for each server running indexing or search queries in the farm.

Start the Office SharePoint Server Search service on each server that will run search queries or indexing

  • [Setup] Open the command line, and then run the following command:

    stsadm -o osearch -action start -role <OsearchRole>-farmcontactemail <FarmContactEmail> -farmserviceaccount <DomainName\UserName> -farmservicepassword <password> -farmcontentaccessaccount <DomainName\UserName> -farmcontentaccesspassword <password>

NoteNote:

farmserviceaccount is the server farm account. farmcontentaccessaccount is the Office SharePoint Server Search service account. role specifies what type of server role the server plays. The values for OsearchRole can be "Index", "Query", or "IndexQuery".

You must create a Shared Services Administration site Web application for the SSP.

Create the content database and the Web application for the Shared Services Administration site

  1. [DBA] Create the Shared Services Administration site 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 SSP service account to the Users group and then to the db_owner role for the Shared Services Administration site content database.

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

    stsadm.exe -o extendvs -url <url> -donotcreatesite -exclusivelyusentlm -databaseserver <DatabaseServerName> -databasename <DatabaseName> -apidtype configurableid -description <IISWebSiteName> -apidname <AppPoolName> -apidlogin <DomainName\UserName> -apidpwd <password>

NoteNote:

url is the URL (in the form http://hostname:port) of the Shared Services Administration site Web application. databasename is the content database for the Shared Services Administration 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 application pool in IIS. apidlogin is the identity for the application pool in IIS. This is the application pool process account. If you are using Kerberos v5 authentication rather than NTLM authentication, use the negotiate parameter rather than the exclusivelyusentlm parameter

Important:

This command must be run on the same computer that is indicated in the url parameter. This is the same computer that is running the Shared Services Administration 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.

  1. [Setup] Open the command line, and then run the following command to restart IIS: iisreset /noforce.

The following procedure will have to be performed once for each portal site in the farm.

Create and configure the portal site Web application 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 Microsoft SQL Server Management Studio, add the SSP Service account to the Users group and then to the db_owner role for the portal site Web application content database.

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

    stsadm.exe -o extendvs -url <url> -donotcreatesite -exclusivelyusentlm -databaseserver <DatabaseServerName> -databasename <DatabaseName> -apidtype configurableid -description <IISWebSiteName> -apidname <AppPoolName> -apidlogin <DomainName\UserName> -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. If you are using Kerberos v5 authentication rather than NTLM authentication, use the negotiate parameter rather than the exclusivelyusentlm parameter.

Important:

This command must be run on the same computer that is indicated in the url parameter. This is the same computer that is running the 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.

  1. [Setup] Open the command line, and then run the following command to restart IIS: iisreset /noforce.

The following procedure must be performed once for the SSP.

Create and configure the SSP content database and SSP Search database, and then create and configure the SSP

  1. [DBA] Create the SSP content database and the SSP 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. [DBA] Using Microsoft SQL Server Management Studio, add the following accounts to the Users group and then to the db_owner role in both databases:

    • Server farm account

    • SSP Service account

    • Windows SharePoint Services Search service account

    • Office SharePoint Server Search service account

    • Application pool process account. This is the Web application pool identity for each Web application associated with the SSP. In this article, this is the Shared Services Administration Web application.

  3. [Setup] Open the command line, and then run the following command to create the SSP (the SSP will use the DBA-created SSP content database and the SSP Search database):

    stsadm -o createssp -title <SSPName> -url <url> -ssplogin <UserName> -ssppassword <password> -indexserver <IndexServerName>-indexlocation <IndexFilePath>-sspdatabaseserver <SSPDatabaseServerName> -sspdatabasename <SSPDatabaseName> -searchdatabaseserver <SearchDatabaseServer> -searchdatabasename <SearchDatabaseName>

NoteNote:

url is the URL (in the format http://hostname:port/ssp/admin) of the Shared Services Administration site. ssplogin is the SSP service account in the format domain\username. indexserver is the name of the server that the index is hosted on. indexlocation is the directory on the index server where the farm administrator specified the index to be stored. By default this is Installation Drive:\Program Files\Microsoft Office Servers\12.0\Data\Office Server\Applications.

Important:

This command must be run on the same computer that is indicated in the url parameter. This is the same computer that is running the Web application. In this article, this is the server where the Shared Services Administration site Web application is running.

NoteNote:

For more information about properly sizing these databases, see Estimate performance and capacity requirements (Office SharePoint Server) and Estimate performance and capacity requirements for portal collaboration environments.

Tags What's this?: Add a tag
Community Content   What is Community Content?
Add new content RSS  Annotations
Processing
© 2008 Microsoft Corporation. All rights reserved. Terms of Use  |  Trademarks  |  Privacy Statement
Page view tracker