Tuning the database server

Tune your database server for optimal performance.

Overview

Your database performs the following functions:
  • Stores all the data that the applications collect and calculate.
  • Stores metadata for configuring and maintaining the database environment.
  • Processes all transactions from the applications.
  • Accesses the data in the database to generate documents.
  • Generates resource-intensive management reports.

Co-location

To improve performance, co-locate the database server on the same subnet as the application and process servers. Do not use cloud database offerings such as IBM Db2 on Cloud Service or Oracle Database Exadata Cloud Service. However, hosting the entire TRIRIGA® infrastructure in the cloud where the infrastructure is hosted on the same subnet is a viable configuration for good performance. In addition, customers report good performance when they use Oracle Exadata Database Machine in on-premises deployments.

Always check the IBM® TRIRIGA Compatibility Matrix for the latest database versions and fix packs that are supported. Performance issues where the database server is not colocated with the application and process servers are not supported.

Converting IBS_SPEC_ASSIGNMENTS to Module Level Associations

TRIRIGA stores all associations between records in the IBS_SPEC_ASSIGNMENTS table. To improve performance, consider converting the IBS_SPEC_ASSIGNMENTS table to Module Level Associations (MLA) tables. MLA tables are smaller and therefore improve performance. MLA tables also reduce database contention in comparison to the IBS_SPEC_ASSIGNMENTS table. For more information, see Converting IBS_SPEC_ASSIGNMENTS to Module Level Associations.

Standard tuning techniques

Apply standard database tuning techniques and periodically monitor production databases during peak load. You can use the standard monitoring tools such as the tools on the database platform. If necessary, adjust parameters to resolve the bottlenecks as suggested by the monitoring tools.