Planning the initial ETL run
You will need to run ETL after you successfully install and configure the product by using the BMC Decision Support for Server Automation Console. ETL populates the empty reports data warehouse with data from one or more BMC Server Automation databases (sites).
Plan the first ETL run carefully because it can be resource intensive and time consuming. 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 how you set the cutoff period while configuring the product.
To prepare for the first ETL run, perform the . After the sizing exercise is complete, ensure the following requirements:recommended by BMC
- The required disk space is allocated for the reports data warehouse.
- CPUs are allocated for the database server.
- Database parameters are set to the correct values (see Recommendations for the Oracle processes parameter and the Microsoft SQL Server documentation for SQL Server parameter recommendations).
The amount of data in your BMC Server Automation 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 BMC Server Automation database for a long time and the database might contain a large amount of data.
When loading data from the BMC Server Automation database into the reports 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 period for the transfer of data needs to balance your business needs for reporting historical data against your time and resource requirements.