Profiler shut down database?????

Note In SQL Server 2005 Service Pack 3 and in later service packs, the processor time stamp is not used. These versions of SQL Server 2005 use a more reliable timer that has a maximum precision of 1 millisecond.

Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

We walk in the dark places no others will enter
We stand on the bridge and no one may pass

Grant Fritchey SSC Guru Points: 398890 More actions · Answer 3

Ah, reading the entire article... what a concept.

"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt

Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning

alen teplitsky SSC-Dedicated Points: 30014 More actions · Answer 4

i did something like this a few times

now i run the profiler to collect the bare minimum information and things like execution plans i check on my own

daryl-547170 Newbie Points: 7 More actions · Answer 5

VERY GOOD information and question.

I can't believe that this isn't more clear or at least some sort of warning when running profiler about what possible problems running regular Profiler could cause.

Very interesting!

SQLBalls SSCarpal Tunnel Points: 4621 More actions · Answer 6

Thanks for the article and all the information, just went through something like this, I was trying to capture some baselines, as well as trace info to run against DTA, and discovered I was the culprit causing time out errors on the server 🙁 Thanks for the solid answers and the recommendations i'm grabbing SQL Server 2005 Performance Tuning and Query Optimization asap.

Twitter: @SQLBalls
Blog: http://www.SQLBalls.com
Channel: https://www.youtube.com/@Tales-from-the-Field

Fraggle-805517 SSCrazy Eights Points: 8907 More actions · Answer 7

It is very good to know that my screw up is benefitting the database society as a whole. 😀 Keep learning.