• State Not Answered
  • Locked Locked
  • Replies 5 replies
  • Subscribers 59 subscribers
  • Views 5027 views
  • Users 0 members are here
Options
Related
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Foglight traces in SQL error log- how do you stop these?

chubbsm
over 5 years ago

 I tried setting the Deadlock collection for every 60 minutes but still showing as every 15 minutes. What process/collection controls this? Can it be modified Enterprise wide, not every agent?

Parents
  • 0 over 5 years ago
    Hi Chubbsm,

    The deadlock collection will reset (stop and start) the trace thread if one of the following options take place:
    A) No event occurred in at least X minute time period (default 30 minutes)
    B). The trace ID does not appear in the SQL Server instance view 'sys.fn_trace_geteventinfo'

    Knowledgebase article 229591 contains a script to change the default from 30 minutes to once per day. Our Support team can also assist with providing a script to making the change for all of the SQL Server agents.

    John
Reply
  • 0 over 5 years ago
    Hi Chubbsm,

    The deadlock collection will reset (stop and start) the trace thread if one of the following options take place:
    A) No event occurred in at least X minute time period (default 30 minutes)
    B). The trace ID does not appear in the SQL Server instance view 'sys.fn_trace_geteventinfo'

    Knowledgebase article 229591 contains a script to change the default from 30 minutes to once per day. Our Support team can also assist with providing a script to making the change for all of the SQL Server agents.

    John
Children
No Data