![]() ![]() For more information on these flags, refer to (v=sql.105).aspx SQL Server Alerts If you want to ensure these flags are enabled at time of starting SQL Server, you’ll need to add -T1204 and -T1222 to your instance’s start up parameters (done via SQL Server Configuration Manager). The following command enables both these flags globally on your SQL Server DBCC TRACEON (1204, 1222, -1) Now to setup a SQL Trace on Deadlock conditions, the Trace Flags you’ll want to enable are 12. For a full list of these flags (and noting that different flags may be SQL version specific), refer to: SQL Server Trace Flags allow you to monitor for specific server conditions and log these events into the SQL server error log. BUT, there is an add-on available which does bridge this gap for the command line impaired Īdmittedly the interface isn’t quite as sexy as the 2012 EE interface, but definitely helps to sooth the burn for those point-and-click DBAs out there ? SQL Server Trace Flags One thing however that many might not be aware is that Extended Events have actually been available in SQL Server since their 2008 release, however via a scripted interface only (which for most makes this much less desirable to use). For reference purposes you can check out the following There’s heaps of details examples available online which step you through setting up a SQL Profiler trace, and even an Extended Events trace via the new 2012 user interface. When looking to identify dead lock conditions for instance, some of your options include As with anything in SQL Server, there’s always multiple ways to approach any problem you come across. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |