The attempt to like a GUI falls flat again.
A first experience with creating stored proceedures.
So every client I support has issues with stagingprop at some point. The vast majority of them are due to mistakes made in the development process. Many developers do not fully understand what stagingprop does, so here's a general description that might help.
I was happy to see the new workload registry variable in Commerce 7/DB2 9. Mostly out of laziness – it requires fewer variables to be set manually, but it also ensures that nothing major is missed (I imagine they may come up with more that won’t be added to the workload registry variable in real time). I had a whole argument with whichever part of IBM a client brought in to do a load-test performance review because I had set one of the paramters to “ON” instead of “YES”. I recently ran across this statement in the Info Center:
I'm just this guy, you know? Ok, so I'm female, but I don't work for IBM and I'm not trying to sell you anything.
DB2 GUIs Suck for a variety of reasons - use the command line.
IN-lists are poor performers. Here's what they look like in explain plans and why they perform poorly.
Several times I've figured things out in my career and thought "how did I ever call myself a DBA without knowing that?"