Quote:
Originally Posted by meromana
Yipes! Now I'm scared! 
Doubting that anyone but you or I cares about this, but...
I think the problem is that the company I work for is so huge that there is a rotation of DBA's who see my queries running. I will make peace with one, explaining that my query is indeed as tweaked as it can be, and I'm running after hours, etc., but then the next day, it will be a different guy, and the next day, yet another. So I just cut & paste my response from one to the next...
--Maria |
You sound is if you are getting newbies sent out as sacrificial lambs on the altar of the PO'ed enduser. You might want to consider getting the big dogs involved.
Next time, ask them what the skew factor is when you run your biggies. If it's more than, say, 20, ask them when was the last time they ran statistics on the tables in your queries. (even 20 is kind of high) Or if they could create a secondary index on key tables in the query just for you. If your queries are as big a PITA as they say and you run them on a regular basis, then they should be willing to create special statistics or indexes just for these queries.
Chances are, your queries are accessing or joining on a column that has no statistics or indexes on it and forcing the parser to read every record in one or more tables and in HUGE tables, that can take some time.
Of course, they'll try to talk you out of it "If we do it for you, we have to do it for everyone". Of course the correct reply is, "only if you go blabbing to the other users"