Diving a bit deeper into examples where an application design that used to be efficient can become overly expensive.
Microservice architectures are trending. We need to consider how this impacts the performance of our applications and the databases we build to support them.
This article is one in a series that focuses on improving performance in Db2 Warehouse. The first part provides some background information and lays out the first and most important aspect of query optimization, namely, cardinality estimation or estimating the number of rows in an execution plan.
This article will help DB2 DBAs and Users to proactively monitor their most critical and live systems on continuous basis without any impact to production and analyze the data on key points to identify any possible DB2 health/hang/performance issues and fix them.
Whenever a performance problem arises, the database takes the blame, but is that really true? This article will provide a hand's on, step by step approach to determine where the problem is. "Guilty Until Proven Innocent"