When running I sometimes find the same thing. I may perceive that my body isn't responding. When I feel that way I try to push a little harder and I usually run considerably faster. Maybe a perceived problem could be worth checking into as well with SQL server - you could make it better as well.

Jason AKA CirqueDeSQLeilI have given a name to my pain...MCM SQL Server, MVPSQL RNNR

Heh... when a patient comes in with a bone sticking out of the skin, guess what's wrong.

I agree... too many people treat symptoms on SQL Server and, many times, they'll treat slow servers with new hardware without correctly identifying what the problem actually is. These same people are frequently grossly diappointed that their new wizz-bang server doesn't do much better than their old one did. Baselines don't help such people because they're not "doctors" and they sometimes just don't know what the symptom of a change compared to a baseline actually means. Worse than that, these same people are terrible "patients" because they don't want to take the necessary "medicine" especially when the correct treatment involves rewriting code.

So far as the question of how to define if the server is slow, it's kind of like defining the difference between a leak and flooding on a submarine. If you find it, it's a leak. If it finds you, it's flooding.

--Jeff Moden"RBAR is pronounced "ree-bar" and is a "Modenism" for "Row-By-Agonizing-Row".

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."

(play on words) "Just because you CAN do something in T-SQL, doesn't mean you SHOULDN'T."--22 Aug 2013