|
-
Guys... I still don't get it.
Poster has a single query which performance is loosing steam. "Used" to run OK, now is getting lazy.
Tell me the truth, when this happens in your own shop... is the first thing you do to go and check physical layout?
Wouldn't any fo the following actions come before looking at physical layout in you standard troubleshooting approach??? 1) Explain plan the query and comopare it with baseline (if you have it)... 2) Look if performance stats are up-to-date... 3) Review Change Control logs looking for what changed since the query was performing OK... 4) Trace the query... 5) Look at run book looking for new processes added since query was performing OK... /// Etc Etc Etc
Shouldn't you be aware of any disk bottle neck well in advance and not waiting for a crappy piece of SQL to sound the alarm? Believe me, in our shop we know what is happening with our physical I/O without having to wait for a query to blow it out.
Pablo (Paul) Berzukov
Author of Understanding Database Administration available at amazon and other bookstores.
Disclaimer: Advice is provided to the best of my knowledge but no implicit or explicit warranties are provided. Since the advisor explicitly encourages testing any and all suggestions on a test non-production environment advisor should not held liable or responsible for any actions taken based on the given advice.
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
-
Forum Rules
|
Click Here to Expand Forum to Full Width
|
Reply With Quote