Tell me about the issue and I’ll help you find the solution you need.
FIX: DBCC CHECKDB/CHECKTABLE command may take longer in SQL Server 2012 or SQL Server 2014
Content provided by Microsoft
Applies to: Microsoft SQL Server 2012 Service Pack 2Microsoft SQL Server 2012 DeveloperMicrosoft SQL Server 2012 EnterpriseMicrosoft SQL Server 2012 StandardMicrosoft SQL Server 2014 DeveloperMicrosoft SQL Server 2014 DeveloperMicrosoft SQL Server 2014 EnterpriseMicrosoft SQL Server 2014 EnterpriseMicrosoft SQL Server 2014 StandardMicrosoft SQL Server 2014 StandardMicrosoft SQL Server 2014 Service Pack 1Microsoft SQL Server 2014 DeveloperMicrosoft SQL Server 2014 DeveloperMicrosoft SQL Server 2014 EnterpriseMicrosoft SQL Server 2014 EnterpriseMicrosoft SQL Server 2014 StandardMicrosoft SQL Server 2014 StandardMore
When you run the DBCC CHECKDB/CHECKTABLE command, the data purity checks can cause the command to unexpectedly run a long time. This problem occurs for the DBCC CHECKDB/CHECKTABLE command in the following circumstances:
Assume that you have database or table that contains SQL CLR User-Defined type (UDT) data in Microsoft SQL Server 2012. SQL Server is not reusing the internal blob memory correctly during the validation of the SQL CLR UDT.
The granted memory for the DBCC operations (checktable or checkdb per table) is estimated incorrectly on large-memory servers.
This problem can cause excessive memory and CPU consumption.
Service pack information
To resolve this issue, obtain the following Service Pack for SQL Server.
Each new cumulative update for SQL Server contains all the hotfixes and all the security fixes that were included with the previous cumulative update. We recommend that you download and install the latest cumulative updates for SQL Server: