Have you ever looked at a list of tables in your database, only to see the set of EXPLAIN tables present in two, five or even 10 different developers’ schemas?
I don’t know about you, but this drives me crazy.… Read the restContinue reading »
Current statistics are vital to performance. If I’m encountering a database I haven’t regularly been supporting, and don’t know the maintenance plans and schedules, I frequently query to get an idea of how current they are.
To report the dates of statistics collection and the number of tables statistics were collected for on each date.… Read the restContinue reading »
I wrote a developerWorks article on finding problem SQL in your package cache. But I refine and play with my SQL over time, so I thought I’d share the version I’ve been using recently.
To find problem SQL in the Package Cache across several importance performance categories.… Read the restContinue reading »
I have been playing a fair amount lately with clustering indexes and have been rehashing my views on reorging tables on an index. This is still a work in progress, but thought I’d share some details and see if others out there have any thoughts to share with me and others on it.… Read the restContinue reading »
This was really a revelation for me when I took DanL‘s SQL workshop before the IDUG conference in Phoenix.
I started out as a physical or systems DBA at IBM, and until studying for certification, I hardly wrote a statement more complicated than
select * from syscat.bufferpools… Read the rest
This technote caught my eye when @db2_support tweeted it the other day ago. It was titled as “DB2 might choose a sub-optimal query execution plan due to distribution statistics”. The title alone intrigued me. As I read through, I thought that I needed to do a bit of investigation to better understand the issue.… Read the restContinue reading »
Like many applications, WebSphere Commerce puts all tables in
USERSPACE1 unless they need larger page sizes. This actually works just fine for smaller and midrange implementations, but we have about one build a year that requires something else – either because of standards that client DBAs adhere to or because they actually are busy enough for I/O and separate buffer pools to matter.… Read the rest
There are a a vast array of things you can do in SQL. But just because you can doesn’t always mean that you should.
I recently ran into an interesting situation with FETCH FIRST ROW ONLY.
The day after new code was deployed, a production database system that usually runs with 40% CPU utilization or less was suddenly pegged at 100% CPU utilization.… Read the restContinue reading »
Sometimes just using the index advisor and a bit of common sense, you can address SQL performance issues. But other times, you have to dig a bit deeper.
I recently found the following query and 300 of its closest cousins (differing only in the length of the second in-list) were eating 30% of the CPU time used by queries on a rather busy database.… Read the restContinue reading »