Question

We have quite a few dataloading processes that run throughout the day all day long. These processes are setting the 610 flag on for their connection then turning it off when they are done. Because these messages are put into the ERROR LOG, our ERROR LOG is growing quite a bit. We've tried using the WITH NO_INFOMSGS parameter of DBCC but it still puts the entry in the ERROR LOG (even though it doesn't put it in the query output).

Any ideas?

The messages look like this:

Date 10/23/2014 8:32:46 AM Log SQL Server (Current - 10/23/2014 8:31:00 AM)

Source spid57

Message DBCC TRACEON 610, server process ID (SPID) 57. This is an informational message only; no user action is required.

...

Date 10/23/2014 8:32:54 AM Log SQL Server (Current - 10/23/2014 8:31:00 AM)

Source spid57

Message DBCC TRACEOFF 610, server process ID (SPID) 57. This is an informational message only; no user action is required.

Was it helpful?

Solution

Licensed under: CC-BY-SA with attribution
Not affiliated with dba.stackexchange
scroll top