Database types and descriptions (Office SharePoint Server)

Applies To: Office SharePoint Server 2007

This Office product will reach end of support on October 10, 2017. To stay supported, you will need to upgrade. For more information, see , Resources to help you upgrade your Office 2007 servers and clients.

 

Topic Last Modified: 2015-03-09

In this article:

  • Office SharePoint Server 2007 deployed in a server farm environment

  • Office SharePoint Server 2007 deployed in a stand-alone environment

This article provides information about the database types and their descriptions, such as configuration, search, and content database. It provides details about the name, purpose, location, and restoration of databases that are created by using Microsoft Office SharePoint Server 2007 in a server farm or stand-alone environment.

Note

The database names specified in the tables in this article are the default names for the databases. You can specify the name of the database, when you create it, except SharePoint_AdminContent_GUID database.

Office SharePoint Server 2007 deployed in a server farm environment

When you install Microsoft Office SharePoint Server 2007 for a server farm, the database server must be running Microsoft SQL Server 2008, Microsoft SQL Server 2005 or Microsoft SQL Server 2000 with the latest service pack installed. You do not need to set up or create specific databases for Office SharePoint Server 2007. The Office SharePoint Server 2007 Setup program creates the necessary databases when you install and configure Office SharePoint Server 2007.

After installation

The following table lists the name, purpose, location, and restoration information for databases that are created when you install Office SharePoint Server 2007 in the server farm environment.

Default database name Purpose Location

SharePoint_AdminContent_GUID

Content databases store all Office SharePoint Server 2007 content. Use the SharePoint Central Administration Web site to add new databases.

Note

When provisioning the initial configuration database, we recommend that you create the administration database by using a name other than _GUID. For example: psconfig -cmd configdb -create -server <SQL Server Alias> -database <CustomerConfiguration> -user <Domain>&lt;Username> -password <Password> -admincontentdatabase <Customer>_Administration_Content>>

<install drive>\%PROGRAMFILES%\Microsoft SQL Server\MSSQL.1\MSSQL\Data

SharePoint_Config

The configuration database contains data about all the databases used, all Internet Information Services (IIS) Web sites or Web applications, solutions, Web Part packages, site templates, and Web application and farm settings specific to SharePoint technologies, such as default quota, blocked file types, and configuration.

<install drive>\%PROGRAMFILES%\Microsoft SQL Server\MSSQL.1\MSSQL\Data

After creating a Web application

The following table lists the name, purpose, location, and restoration information for databases that are created when you create a Web application.

Default database name Purpose Location

WSS_Content

This database contains data specific to a Web application and its site collections. It contains the content data, such as a document uploaded to a list or a library. By default, a single content database is created for each Web application. As new site collections are added to a Web application, the content for that site collection is stored in the database assigned to the parent Web application.

<install drive>\%PROGRAMFILES%\Microsoft SQL Server\MSSQL.1\MSSQL\Data

After starting the search service

The following table lists the name, purpose, location, and restoration information for databases that are created when you start the search service.

Default database name Purpose Location

WSS_Search

This database is used for the search services. It contains the information that is required for searching content.

<install drive>\%PROGRAMFILES%\Microsoft SQL Server\MSSQL.1\MSSQL\Data

After creating an SSP

The following table lists the name, purpose, location, and restoration information for databases that are created when you create a Shared Services Provider (SSP).

Default database name Purpose Location

SharedServicesN_DB

Each SSP requires a database for service-specific data.

<install drive>\%PROGRAMFILES%\Microsoft SQL Server\MSSQL.1\MSSQL\Data

SharedServicesN_Search_DB

In addition to the SSP database, a separate database is required for frequently changing search-related data.

<install drive>\%PROGRAMFILES%\Microsoft SQL Server\MSSQL.1\MSSQL\Data

After server setting for single sign-on

The following table lists the name, purpose, location, and restoration information for databases that are created when you specify settings for single sign-on (SSO).

Default database name Purpose Location

SSO

This database stores the settings and account information for single sign-on.

<install drive>\%PROGRAMFILES%\Microsoft SQL Server\MSSQL.1\MSSQL\Data

Office SharePoint Server 2007 deployed in a stand-alone environment

When you deploy Office SharePoint Server 2007 on a single server by using the default settings, the Setup program automatically installs Microsoft SQL Server 2005 Express Edition and uses it to create the configuration database and content database for the SharePoint sites. In addition, the Setup program creates an SSP, installs Central Administration, and creates the first site collection and site.

After installation

The following table lists the name, purpose, location, and restoration information for databases that are created when you install Office SharePoint Server 2007 in a stand-alone environment.

Default database name Purpose Location

SharePoint_AdminContent_GUID

Content databases are used to store all Office SharePoint Server 2007 content. You can add new databases by using Central Administration.

<install drive>\%PROGRAMFILES%\Microsoft Office Servers\12.0\Data\MSSQL.N\MSSQL\Data

SharePoint_Config

The configuration database contains data about all the databases used, all of the IIS Web sites, Web applications, solutions, Web Part packages, site templates, and Web application and farm settings specific to SharePoint technologies, such as default quota, blocked file types, and configuration.

<install drive>\%PROGRAMFILES%\Microsoft Office Servers\12.0\Data\MSSQL.N\MSSQL\Data

SharedServicesN_DB

Each SSP requires a database for service-specific data.

<install drive>\%PROGRAMFILES%\Microsoft Office Servers\12.0\Data\MSSQL.N\MSSQL\Data

SharedServicesN_Search_DB

In addition to the SSP database, a separate database is required for frequently changing search-related data.

<install drive>\%PROGRAMFILES%\Microsoft Office Servers\12.0\Data\MSSQL.N\MSSQL\Data

SharedServicesContent

This database is dedicated for the shared services content.

<install drive>\%PROGRAMFILES%\Microsoft Office Servers\12.0\Data\MSSQL.N\MSSQL\Data

WSS_Content

This database contains data specific to a Web application and its site collections. It contains the content data, such as the document uploaded to a list or a library. By default, a single content database is created for each Web application. All new site collections added to a Web application use the same database.

<install drive>\%PROGRAMFILES%\Microsoft Office Servers\12.0\Data\MSSQL.N\M MSSQL\Data

WSS_Search_ComputerName

This database is used for the search services. It contains the information that is required for searching content.

<install drive>\%PROGRAMFILES%\Microsoft Office Servers\12.0\Data\MSSQL.N\MSSQL\Data

After server setting for single sign-on

The following table lists the name, purpose, location, and restoration information for databases that are created when you specify settings for single sign-on.

Default database name Purpose Location

SSO

This database stores the settings and account information for single sign-on.

<install drive>\%PROGRAMFILES%\Microsoft Office Servers\12.0\Data\MSSQL.N\MSSQL\Data

See Also

Concepts

General reference (Office SharePoint Server)
Installation points for Office SharePoint Server 2007
SharePoint Timer job reference (Office SharePoint Server)
Temporary files created during backup, import/export, and upgrade (Office SharePoint Server)