![]() ![]() The Blocked Process Report shows you the “input buffer” of the commands involved - it may be partial information and not the full text of the query. This has been in SQL Server for a long time, and it’s extremely useful. I like to use the built-in Blocked Process Report for this. We need SQL Server to give us more information on who is involved in the blocking. I have example code to create blocking and deadlocks for your dev environments in my post, Deadlock Code for the WorldWideImporters Sample Database.įor production databases, you can create a temp table and write similar code to create blocking in those.įinding the queries involved with the Blocked Process Report I highly recommend that, so you don’t get an inbox of alerts every 20 secondsĬreate some blocking in a test database or in tempdb and make sure the alert works. You can configure the alert to only fire every X minutes.If you really need something more sensitive and reliable, you need a monitoring system fully independent / outside of the SQL Server to be polling in and checking it for availability and performance.It will only poll every 15-30 seconds, and there’s no published guaranteed SLA on that polling frequency. The SQL Agent doesn’t poll counters constantly - and we want this to be lightweight, so that’s a good thing. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |