General recommendations

You can tune Business Intelligence to help performance.

This topic provides general recommendations on how to tune Business Intelligence.

Table 1. General recommendations for tuningBusiness Intelligence
Recommendation Comment
Network Ensure that all Business Intelligence servers are on the same LAN gigE or higher switch to avoid traffic through uplinks or inter-switch links.
ETL’s (Extract, Transform, and Load)
  • Run smaller ETL’s more frequently during the day instead of running one large extraction at night. The large extractions will be heavier, the sorts will be exponentially larger, and the potential impact to the standby or OLTP database greater. Also, missing a large ETL will make the catch up harder and longer.
  • ETL’s at low volumes can run against the OLTP. At higher volumes, extraction should go to a non-OLTP transactional database (e.g., the Disaster Recovery standby or a second read-only replica).
  • ETL’s at the higher volumes to the OLTP can impact OLTP, can result in snapshot too old (Oracle), and increase I/O contention.
  • Run ETL’s once per day or more frequently, depending on business requirements. ETL’s may run as frequently as every hour. The exception to this rule is the aggregate load ETL. Instead of running the aggregate load with every incremental ETL, run the aggregate load ETL once per day, during the quiet period.