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.

Planning the initial ETL run

This topic provides guidelines for planning the first ETL run after you install 

The macro unmigrated-inline-wiki-markup from Confluence is no longer available.

.

As described in Configuring-after-installation, you must run ETL after you successfully install the product. The first ETL run can be very resource intensive and time consuming because ETL populates the empty reports data warehouse with data from one or more 

The macro unmigrated-inline-wiki-markup from Confluence is no longer available.

databases (sites).

The amount of time and database resources needed for the initial data load depends on the data volume in the BMC Server Automation databases and whether and how you use the set_etl_cutoff.nsh script.

To prepare for the first ETL run, you can perform the data warehouse sizing exercise recommended by 

The macro unmigrated-inline-wiki-markup from Confluence is no longer available.

. After the sizing exercise is complete, ensure the following:

  • The required disk space is allocated for the data warehouse.
  • CPUs are allocated for the database server.
  • Database parameters are set to the correct values (see Recommendations-for-the-Oracle-processes-parameter for Oracle processes parameter recommendations and the Microsoft SQL Server documentation for SQL Server parameter recommendations).

The amount of data in your 

The macro unmigrated-inline-wiki-markup from Confluence is no longer available.

database varies based on how long you have been storing data, whether cleanups have been run, and how much data you store in the database. Data could have been accumulating in the 

The macro unmigrated-inline-wiki-markup from Confluence is no longer available.

database for a long time and the database might contain a large amount of data.

When loading data from the 

The macro unmigrated-inline-wiki-markup from Confluence is no longer available.

database into the data warehouse for the first time, it is important to determine how far back in time you need data for your reports. The decision influences the database sizing process and the amount of time needed for the first ETL run. Consequently, your decision about setting a cutoff date for the transfer of data might need to be a balance between your business needs for reporting historical data and your time and resource requirements.

After you determine how much historical data you want to include in your reports, you can use the set_etl_cutoff.nsh script to limit the amount of data transferred during the initial ETL run. For details about using this script, see Specifying-ETL-cut-off-dates.

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*