Unsupported content

 

This version of the documentation is no longer supported. However, the documentation is available for your convenience. You will not be able to leave comments.

Sizing for existing product installations and existing BMC Server Automation installations

If you are currently using 

    MultiExcerpt named 'BladeLogic' was not found
The multiexcerpt named 'BladeLogic' was not found. Please check the page name and MultiExcerpt name used in the MultiExcerpt Include macro. and
    MultiExcerpt named 'Product_Name' was not found
The multiexcerpt named 'Product_Name' was not found. Please check the page name and MultiExcerpt name used in the MultiExcerpt Include macro., use the instructions in this topic to determine the size requirements for your reports data warehouse and archived data. 

A script gathers the data needed to determine your database size and archival data size requirements from the reports data warehouse database. After you run the script, the HTML output shows the size requirements.

Before you begin

Download the required files, as described in Sizing tools.

To determine your reports data warehouse and archival data size requirements 

  1. Log on to the reports data warehouse database as the reports data warehouse user.

  2. Run the appropriate script for your database type:
    • Oracle:

      sqlplus <user>/<password>@<TNS_ENTRY> @bds_dbsizing_for_existing_bds_oracle.sql bds_dbsizing_for_existing_bds_oracle.html
      • <user> and <password> are the reports data warehouse user name and password.

      • <TNS_ENTRY> is the database TNS entry name.
    • Microsoft SQL Server:

      sqlcmd -S <server>\<instance> -d <ReportsWarehouseDatabaseName> -U <user> -P <password> -i bds_dbsizing_for_existing_bds_sqlserver.sql -o bds_dbsizing_for_existing_bds_sqlserver.html -h-1
      • <server> is the reports data warehouse database server name.

      • <instance> is the name of the database instance.
      • <user> and <password> are the database user name and password.

        The script generates a file named bds_dbsizing_for_existing_bds_oracle.html (for Oracle) or bds_dbsizing_for_existing_bds_sqlserver.html (for SQL Server) in the directory from where you executed the script.

The Oracle HTML output file provides the following information:

  • Number of
      MultiExcerpt named 'BladeLogic' was not found
    The multiexcerpt named 'BladeLogic' was not found. Please check the page name and MultiExcerpt name used in the MultiExcerpt Include macro. sites considered for calculation
  • Number of managed servers in the existing environment
  • Number of days for which data was available for calculation
  • Number of days in the past for which server growth is considered for projecting requirements in the next six months and one year
  • Disk space (in GB) currently being consumed by each tablespace in the reports data warehouse
  • Projected disk space (in GB) required by each tablespace in the next six months and one year
  • Disk space (in GB) required for the archived data

The SQL Server HTML output file provides the following information:

  • Number of managed servers in the existing environment
  • Number of days for which data was available for calculation
  • Number of days in the past for which server growth is considered for projecting requirements in the next six months and one year
  • Disk space (in GB) currently being consumed by the data file and log file in the reports data warehouse
  • Projected disk space (in GB) required by data file and log file in the next six months and one year
  • Disk space (in GB) required for the archived data

If you need to increase the database size, use the instructions provided by your database vendor.

Note

This sizing process calculates the size requirements based on one BMC Server Automation site. If you are using more sites, the size requirements increase proportionally.

Related topics

Sizing for new product installations and new BMC Server Automation installations
Sizing for new product installations and existing BMC Server Automation installations

This version of the documentation is no longer supported. However, the documentation is available for your convenience. You will not be able to leave comments.

Comments