Initially this tool had no GUI and could be set from complex code but from SQL Server 2012, with an introduction of GUI, this is a preferred tool for gathering query performance metrics among other tools. It is very useful tool to be used on production server.
It allows to configure itself in any way so that user can collect all or only selective information as needed. Extended Events What is extended events?Įxtended events is a performance monitoring tool introduced in SQL Server 2008, which uses very few resources and provides very high configurable architecture. Extended events are very useful in such types of scenarios like capturing data from production server. We can create a session and start it to capture only those events in which we are interested. Extended events are very useful because of very few resource utilization. If we don’t have any clue about deadlock being occurred in midnight at our production server and because of heavy load on server, we can not use SQL Server Profiler their.
We use these events to capture interested information to be analyzed now or later from heavy load servers (Like production server). These events are less resource intensive and light weight in comparison of SQL Server Profiler. Now in this post we are going to learn a very useful method of tracing deadlock with Extended Events.
#MONITOR DEADLOCK SQL SERVER 2012 HOW TO#
In last two articles, we have learned how to capture deadlock using SQL Server Profiler and Tracing deadlock with Trace Flag 1222 and Trace Flag 1204.
0 kommentar(er)
