Export (0) Print
Expand All
1 out of 1 rated this helpful - Rate this topic

Inventory of SQL Server databases for a typical Project Server 2007 deployment

Project Server 2007

This document describes the databases that are created once Microsoft Office Project Server 2007 and Microsoft Office Project Portfolio Server 2007 are installed. The following table specifies the databases that are used, assuming you install both Office Project Portfolio Server 2007 and Office Project Server 2007 on a Microsoft Office SharePoint Server 2007 farm and that they both share the same instance of SQL Server.

Product Database name Description Requirement Related documentation

Office SharePoint Server 2007

SharePoint Farm Configuration

SharePoint configuration database (only one per farm).

Required

Deploy using DBA-created databases (Office SharePoint Server)

SharePoint Central Administration Content

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

Required

Shared Services Provider (SSP) Administration Database (n)

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

Required

Shared Services Provider Content Database (n)

SSP Content database.

Required

Shared Services Provider Search Database

SSP Search database (one per SSP).

Required

Portal site Web application content database (n) — PWA Site Collection

You need a content database for each SharePoint site; we recommend having a dedicated site collection to host Project Web Access.

Required

Portal site Web application content database (n) — PWA Workspaces

A separate site collection/content database to store all project workspaces. This helps with backup/restore and general data isolation from the rest of the farm.

Recommended

Portal site Web application content database (n) — My Sites

A dedicated content database to store “My Site” content; refer to the link at right for other best practices.

Recommended

Best practices for My Sites

Office Project Server 2007

Archive Database (n)

Saves backed-up and older versions of projects.

Required

Plan the database tier

Draft Database (n)

Contains tables for saving unpublished projects from Microsoft Office Project Professional 2007. Project data in the Draft database is not accessible by using Office Project Web Access.

Required

Plan the database tier

Published Database (n)

Contains all of the published projects. Published projects are visible in Office Project Web Access. The Published database also contains tables that are specific to Office Project Web Access (timesheets, models, views, and so on), and global data tables (outline codes, security, and metadata).

Required

Reporting Database (n)

The staging area for generating reports and online analytical processing (OLAP) cubes. Data in the Reporting database is updated nearly in real-time, is comprehensive, and is optimized for read-only report generation.

Required

Office Project Portfolio Server 2007

PPS Account Data

Contains the actual account data, such as the project, application, program and portfolio data, related cost and resource information, optimization scenarios, and other data. Even though this database can contain information from multiple accounts, we recommend having only one account per database to ease future upgrades or database migrations. For more information about setting up multiple accounts, see the "Creating multiple accounts" section of the Office Project Portfolio Server 2007 Deployment Guide.

Required

Microsoft Office Project Portfolio Server 2007 Deployment Guide

PPS AccountIndex

Contains information about the defined accounts in Office Project Portfolio Server 2007. Each account acts like a single instance of Office Project Portfolio Server 2007. Information cannot be shared across multiple accounts. For more information about setting up multiple accounts, see the "Creating multiple accounts" section of the Office Project Portfolio Server 2007 Deployment Guide.

Required

Microsoft Office Project Portfolio Server 2007 Deployment Guide

SQL Reporting Services 2005/2008

Report Server database: “ReportServer”

Used for primary storage of all SSRS data (reports, security settings, and so on).

Required (for Office Project Portfolio Server 2007)

Creating a Report Server Database

Report Server catalog: “ReportServerTempDB”

Used to store all temporary data.

Required (for Office Project Portfolio Server 2007)

Creating a Report Server Database

SQL Server Analysis Services 2005/2008

Analysis Services Repository

Used to store OLAP metadata ("OlapObjects”) (for example, cubes and dimensions).

Recommended

Requirements for using SQL Server 2005 Analysis Services with the Project Server 2007 Cube Building Service

ASP.NET

aspnet

Membership provider database. It’s used to store all user account/password for users that are not part of Active Directory for instance.

Required (if you are using forms-based authentication)

Configure SQL Membership Provider forms authentication for Project Server 2007

The notation “(n)” in the "Database name" column means that you could have multiple databases, depending on your configuration (for example, multiple PWA instances).

NoteNote:

For one instance of Office Project Web Access created on an Office SharePoint Server 2007 farm with Office Project Portfolio Server 2007 and SQL Reporting Services all sharing the same SQL Server instance, you will typically have 18 relational databases. If you have another PWA instance, another SharePoint site, another SSP, Microsoft Office PerformancePoint Server 2007, and so on, you should expect additional databases. We recommend you carefully plan your EPM deployment and architect your solution based on the above recommendations and the latest TechNet content for all these products.

Did you find this helpful?
(1500 characters remaining)
Thank you for your feedback
Show:
© 2014 Microsoft. All rights reserved.