During his involvement with a large compliance project the presenter, as well as designing a reasonable sized enhancement to the largest database in the shop, had to expand his knowledge and dip into the rich set of features available to provide the overall database solution utilised in terms of DB2
This week we continue our theme of improving application performance by reducing the number of calls to DB2. In addition to using DB2 techniques, we look at programs that retrieve more data than they really need, retrieve data sooner than it is needed, and retrieve the same data multiple times.
Sometimes we forget. It isn’t so much getting older (I hope) but more that we continue to get busier and busier. With the rush to pick up and handle the new tasks that are thrown our way we sometimes miss the basics. Application design that takes into account performance is one of those basics...
Most relational tuning experts agree that the majority of performance problems with applications that access DB2 are caused by poorly coded programs or improperly coded SQL. A great deal of time is spent on tuning your SQL but how much time are you spending tuning or conducting performance reviews o
Scenario – your query is performing poorly. You see DB2 picked an access path that is less than optimal. First you make sure there are appropriate indexes. You look to see if the statement is written in a way that enables DB2 to use those indexes. Then you check the Filter Factors of the predicates.