We have a SQL Server 2014 with 140 user databases, each of which have approx. 180 tables.
A maintenance plan was scheduled for once a week but it was discovered that the Check Database Integrity (DBCC CheckDB
) job was taking too long. The schedule was disabled, the job stopped and the process killed.
However, we are now seeing DBCC TABLE CHECK
command running on multiple threads. The MAXDOP configuration setting has been reduced to give other processes a chance, but the table check is still using as many threads as it can get hold of.
The question is: How to kill this process?
BTW - the server has been rebooted(twice).
select @@version
andselect requested_memory_kb,granted_memory_kb from sys.dm_exec_query_memory_grants where session_id=xx
. Where session_id is session ID of checkdb running.