Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.
The maximum number of running jobs that an SCVMM system should be able to handle is around 10,000 and hitting this many running jobs at one time would be an exceptionally rare occurrence. Should it occur, however, it can have a severe impact on the performance of the SCVMM engine.
The number of retained Jobs count refers to the number of running tasks tracked in the TaskTrail database table in SQL. The size of this database can have as much of an impact on performance as the actual running jobs. If the number of running jobs nowhere reaches 10,000 then it may be that the tombstone limit on entries tracked in the TaskTrail database is too conservative
By default the TaskGC entry in HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft System Center Virtual Machine Manager Server\Settings\SQL is set to tombstone entries at 90 day intervals. If a user is running a number of jobs on a daily basis that would cause the TaskTrail database to exceed this tolerance then this number can be reduced to tombstone entries more often.
By default, a job runs every 20 hours that will read this value and start the process to remove the jobs above the upper recommended limit, however it may take several cycles to bring the total job count down to acceptable limits.
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft System Center Virtual Machine Manager Server\Settings\Sql
2. Create a DWORD value named “TaskGC” and set its value to a number less than 90 (decimal).
(TaskGC value controls the number of days that the events are stored in the DB)
3. Restart the VMM server several times to remove jobs until the total drops below 10,000
This registry key runs a stored procedure on the SQL Server once every 20h. In one run, a maximum of 50,000 objects in the jobs table is deleted. As there are multiple objects per job, this might not show a significant reduction immediately, but will succeed over several days to cleanup the DB.
Alternatively, you may run SQL Manager directly and run the following commands multiple times, until the execution does not find any more objects.
DECLARE @CutoffDateTime datetime
SELECT @CutoffDateTime = '4/1/2009'
EXECUTE [VirtualManagerDB].[dbo].prc_TR_GarbageCollect @CutoffDateTime
Note: You need to adjust CutoffDateTime to a date for your desired history length.
Keywords: vkball, kb