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.
Service pack informationTo resolve this issue, obtain the following Service Pack for SQL Server.
- How to obtain the latest service pack for SQL Server 2012
- How to obtain the latest service pack for SQL Server 2014
Cumulative update informationThe issue was first fixed in the following cumulative update of SQL Server:
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
Article ID: 3029825 - Last Review: Dec 22, 2015 - Revision: 1