We have noticed a serious problem with the monitoring on one of our production servers, the cause of which is SQL Response.
Our understanding of the product that the impact on the monitored servers is minimal, however through its current interaction it is using between 10-15% of the monitored servers CPU at regular intervals to execute the following code.
DBCC TRACEON WITH NO_INFOMSGS
DECLARE @dbccstat TABLE
INSERT INTO @dbccstat EXEC('DBCC TRACESTATUS(1204, -1) WITH NO_INFOMSGS')
DECLARE @status INT
SELECT @status = Status FROM @dbccstat
IF @status = 0
DBCC TRACEON( 1204, -1 ) WITH NO_INFOMSGS;
Can you advise on this? As in the current setup this renders sql response un-usable for us in a production environment as CPU usage is at a premium.