If you have read my previous post on how to capture the Blocked Process Report event then checkout this script that queries the data captured in the event
Query and Analyze SQL Server’s Blocked Process Report event Read More »
For the TraceBlockedProcessReport stored procedure presented in this post see my Traces project at GitHub. This is from the Microsoft’s official documentation “The Blocked Process Report event class indicates that a task has been blocked for more than a specified amount of time. This event class does not include system tasks or tasks that are
Capture SQL Server’s Blocked Process Report event Read More »
This is a link to previous related posts that you may find interesting https://sqlserverutilities.com/maximize-sql-trace/ https://sqlserverutilities.com/use-sql-trace-to-capture-database-exceptions/ If we want to capture all the commands being sent to the database engine we should capture just these 2 events: SQL:BatchCompleted and RPC:Completed. By doing so we guarantee to be capturing all executions sent to the database engine which
In this post I will discuss and present some practical use cases for SQL Trace also known as “Server Side Trace”. Before we move forward I would like to first make the distinction between SQL trace and SQL Server Profiler. SQL Trace is a database engine technology while SQL Server Profiler is a .NET application
For the previous post discussing SQL Trace see this post For the TraceExceptions stored procedure presented in this post see my Traces project at Github. Capturing all the exceptions that occur in the database engine has been proved to be very useful in my experience. Actually, when thinking about it, I realize most DBAs do
