Day 3–Trace Flag 3688–Suppress Trace information from Errorlog
In one of our development server we will be frequently running trace files to capture information for performance trouble shooting. However this in turn writes so many entries about trace file in errorlog which fills the errorlog. Errorlog entry is big and we are not to search it easily so to avoid the trace information we used trace flag 3688 in startup parameter of SQL Server. Refer KB article http://support.microsoft.com/kb/922578 for more.
You will see similar information like below 2011-08-03 22:04:15.000 spid52 SQL Trace ID 2 was started by login “sa”. 2011-08-03 22:04:16.690 spid53 SQL Trace stopped. Trace ID = ’2′. Login Name = ‘sa’. 2011-08-03 22:04:26.070 spid52 SQL Trace ID 2 was started by login “sa”. 2011-08-03 22:04:27.750 spid53 SQL Trace stopped. Trace ID = ’2′. Login Name = ‘sa’. I’ve added the trace flag to SQL Server as shown below, this change requires SQL Server to get restarted so ensure you have restarted SQL Server service after you added this trace flag. To know full steps for adding trace flag check the article “Enable \ Disable Trace Flag in SQL Server”
Thus you can utilize the trace flag 3688 if you have more number of trace flags running and filling up your errorlog.
Tags: 3688, trace flag, troubleshoot
Trackback from your site.
Comments (3)
DotNetShoutout
| #
Day 3–Trace Flag 3688–Suppress Trace information from Errorlog – SQL-Articles…
Thank you for submitting this cool story – Trackback from DotNetShoutout…
Reply
y4up
| #
Though not many prerequisites but this requires a HOTfix before application, mind your head before doing that. Only thing I counldnt unde1rstand is why would this require the BROWSERservice to be turned off? Is this turning off any kind of sniffing of TDS at SNI (DNN)?
Reply
VidhyaSagar
| #
That’s right! I hope that’s for Server restart, I’m not sure why that’s require. I think if it’s running then you require a server restart. We don’t have a clear picture on what that hotfix does.
Reply