Foglight uses traces to monitor SQL Server databases.
The database agent runs a trace (TRACEWRITE) on the Master database when collecting metrics. It also runs other SQL statements on the Master database that create and drop tables (#ResourceDB, #ObjectResource, etc).
Is it possible to disable the traces and what is the impact?
Beginning with the 5.9.4.20 and higher releases of the SQL Server cartridge, the use of traces as the means to determine deadlocks and SPIDs has been replaced with Extended Events for versions above SQL Server 2008.
This KB article however is still relevant because users the ability to change the default trace mechanism using the Agent Status Properties panel back to the trace functionality.
There are two types of traces:
If the traces are disabled, then Session Trace collection will not work and the Deadlocks collection may not work.
© 2024 Quest Software Inc. ALL RIGHTS RESERVED. Terms of Use Privacy Cookie Preference Center