Databases are a lot like modern automobiles. They need tuning, slow down as workloads increase, and consume more MIPS (Microprocessor without Interlocked Pipeline Stages). Just like cars, when you tune databases, they take a bigger workload, performing well within the limits of SLAs.

Modern automobile engines are highly complex with a multitude of interconnected components that require an experienced mechanic using sophisticated tools. Likewise, DB2 is highly complex. Tuning it requires a skilled technician using sophisticated tools.

My customers have databases and a lot of monitoring tools, as well. It’s very obvious that the market is demanding more monitoring tools, while the tools are growing more complex in parallel to technology. Sometimes customers pay lots of money, but don’t use the product features enough to get the maximum value.

While at Information On Demand, I’ll be delivering a session, “Understanding IBM Tivoli OMEGAMON for DB2 Batch Reporting, Customization and  Tuning Practices” (Session Number IDZ-1155B). I will talk about how to maximize the benefit of DB2 Batch Reporting and tune your DB2 system. Omegamon for DB2 provides a lot of raw data and information about what’s happening inside your DB2 application and DB2 subsystem.

Collecting this valuable data and providing insight about DB2 workload using reporting features and doing this periodically is something very important and necessary. The application development methodologies have been changing. Some customers prefer pushing more business logic inside the database engine itself through Stored Procedures, Triggers and UDFs. Having special features to monitor those code pieces is a rising necessity. I’m also going to mention about how to monitor them through Batch Reports.

I hope to see you there, on Tuesday, October 23 at 1:45 PM in Islander D of the Mandalay Bay Convention Center.