Recently, with some surprise, I learned that in one of the departments of the huge company where I work, the launch of SQL Profiler at business hours.
I do not know how they get out to analyze performance problems that occur just in business hours. After all, performance views often do not give an accurate picture, especially if one / two procedures / queries slow down, without especially loading the server itself. Tiny Queer that runs several times an hour and runs for 10 seconds instead of one (but does very important client very nervous) will definitely not get into DMV views. And select with CROSS APPLY according to the texts of the query itself loads the server very robustly.
However, I am interested in understanding where this fear comes from. In some firms SQL Profiler - a working tool, in some they were afraid of it, like fire (for some time I was engaged in consulting and could compare). I'm pretty sure it went like this:
Houston, we have a problem. The base slows down. figure it out
There are so many ticks here⦠What do I need?
Okay, I'll tick all the boxes and then I'll decide.
What remains in the head of the high authorities? Someone launched SQL Profiler and everything fell into place. And then they tell it to each other over a game of golf.
By the way, the attempt to write down such 'we write everything' traces not to a file, but to the database on the same server - I once witnessed such a case.
And how are things with you? Please take part in the survey
Only registered users can participate in the survey. , you are welcome.
Can you run SQL profiler on PROD?
-
We are a small company, everything is simple for us
-
Production admins can of course
-
Production admins can, after approving and beating
-
Holy holy holy
4 users voted. 3 users abstained.
Source: habr.com