Microsoft SQL Server Sizing Guidelines

The following table describes the Microsoft SQL Server sizing guidelines.

Product

Sizing Guideline

Shared ServicesStart with 100 MB, and add more as the number of migrations with Lifecycle Management and the number of audit records increases.
EPM Workspace The space needed depends on the aggregate size of the objects that you plan to store in the repository. Oracle recommends starting with at least 250 MB, which provides space to expand the EPM Workspace repository without having to increase the data file or tablespace. A shared pool size of 60 MB is used during configuration with EPM System Configurator.
Performance Management Architect

Oracle recommends starting with at least 250 MB.

Administration Services

The space needed depends on the metadata created; Oracle recommends starting with at least 32 MB.

Essbase Studio

The space needed depends on the metadata created; Oracle recommends starting with at least 32 MB.

Planning and Calculation Manager

  • 100 MB for applications with 5,000 or fewer total members

  • 200 MB for applications with 15,000 or fewer total members

    Note:

    You can adjust the size of the system table database to match the size of the application.

Financial Management and Calculation Manager

  • 100 MB for applications with 5,000 or fewer total members

  • 200 MB for applications with 15,000 or fewer total members

    Note:

    You can adjust the size of the system table database to match the size of the application.

Performance Scorecard500 MB
Profitability and Cost ManagementOracle recommends starting with at least 250 MB.
Data Relationship Management

  • Set the initial file size to 1 GB

  • Turn on Auto Growth and set to 10%

FDMSee the Oracle Hyperion Financial Data Quality Management DBA Guide.