⬆️ ⬇️

Is the SQL profiler dangerous?

Recently, with some surprise, I learned that in one of the departments of a huge company where I work, the launch of the SQL profiler during business hours is prohibited.





I do not know how they get out to analyze performance problems occurring just in business hours. After all, performance views often do not give an accurate picture, especially if one / two procedures / checks slow down, especially without loading the server itself. A tiny package that runs several times an hour and works 10 seconds instead of one (but makes a very important client very nervous ) will definitely not get into DMV views. And select with CROSS APPLY on texts, he loads the server very well.



However, it is interesting for me to understand where this fear comes from. In some firms, the SQL profiler is a working tool, in some they were afraid of it, like fire (for some time I was engaged in consulting and could compare). I am pretty sure that it was like this:

')



Houston, we have problems. Brakes the base. Get it right









There are so many ticks here ... What do I need?









Okay, put all the checkmarks and then decide.







What remains in the head of the high authorities? Someone started the SQL profiler and everything fell apart. And then tell it to each other for a game of golf.



By the way, an attempt to write such ' we write all ' traces not into a file, but into a database on the same server gives special pacature - once I witnessed such a case.



And how are things going with you? Participate in the survey please

Source: https://habr.com/ru/post/445004/



All Articles