Howdy group,
@@Version:
Microsoft SQL Server 2012 (SP1) - 11.0.3339.0 (X64)Jan 14 2013 19:02:10
Copyright (c) Microsoft Corporation
Standard Edition (64-bit) on Windows NT 6.1 <X64> (Build 7601: Service Pack 1) (Hypervisor)
I've been using Data Collector on most my servers for a couple years, and never had any major issues until now. For some reason, seemingly random (I just haven't found the pattern yet), collection_set_3_upload job, step 2 will use between 50 and 100% CPU then timeout after an hour. There are no blocks when I look at running processes. I used Extended Events to check out the actual query and it is this WHILE loop playing over and over again.
WHILE @parent_log_id IS NOT NULL BEGIN -- get the next parent SET @log_id = @parent_log_id SELECT @parent_log_id = parent_log_id FROM dbo.syscollector_execution_log_internal WHERE log_id = @log_id; END
56 mins in, it already had 1292279865 READS. The COUNT(*) of my MSDB.dbo.syscollector_execution_log_internal table is only 28,036. Again, there are no waits, it seems it can't find a @parent_log_id and just keeps on going till the 3600 sec timeout.
I've searched for sometime without luck hoping to find a solution. This is only happening on one server. Has anyone else seen this situation? My next step is to try to debug this stored procedure to figure out what is going on.
Thanks!
-John V