Pet peeve... maybe a rant... (please forgive the forthcoming soapbox)... consider this carefully... no matter which "performance monitoring" tool you use, what good does it do you if you find a performance problem when the only people you have to fix the performance problem are the people who wrote the original problem into the code in the first place?
Although I absolutely agree that some basic performance monitoring of the system and the database is essential, I'm sure that most of you would agree that finding a problem with code that way is a bit like closing the gate after the horse got out. Finding out that a production batch job really takes 8 to 12 hours to run instead of the 10 minutes that everyone thought it would is a real wakeup call. Finding out that a new production batch job locks up the server for 10 minutes 4 times a day usually causes a head or two to roll. Finding out that you have a 10 second web latency when only 20 users login, usually causes many people much pain into the wee hours of the morning.
I think that companies spend way too much money on slick performance monitoring "toys" and not enough on good solid Developers and Analysts (GUI, Backend, or combined) that know how to design/write/unit-test performance enabled, highly scalable code nor do they give them enough time to just "do it right". Even if you have magic performance monitoring tools that say things like "the following code caused the problem because it contains a cursor/triangular-join/unnecessary-correlated-subquery/whatever in it", ya gotta have someone that can fix it... the catch 22 usually is, if you did have someone to fix it, it wouldn't have been written to cause a problem in the first place.
I've also found that simple things, like reviews of the code by Peers and DBAs, some good QA testing, and a little performance/scalability testing, go a very long way to keep your performance monitors from paging you at both 2 in the morning and 2 in the afternoon.
Bottom line... if you can get Management to buy into performance monitoring tools, you should also get them to buy into problem prevention... which costs more? ... Doing it right the first time, or monitoring it and reworking it every time it becomes a problem?
Don't kill me folks... I just had to get that off my chest
is pronounced "ree-bar
" and is a "Modenism
" for R
First step towards the paradigm shift of writing Set Based code:
________Stop thinking about what you want to do to a ROW... think, instead, of what you want to do to a COLUMN.
"Change is inevitable... change for the better is not".
"Dear Lord... I'm a DBA so please give me patience because, if you give me strength, I'm going to need bail money too!"
How to post code problems
How to Post Performance Problems
Create a Tally Function (fnTally)