Microsoft distributes Microsoft SQL Server 2012 fixes as one downloadable file. Because the fixes are cumulative, each new release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2012 fix release.
Symptoms
Assume that you have a table that contains more than 2 billion rows in a Microsoft SQL Server 2012 database. You try to build a columnstore index for the table, or you run some queries that scan the columnstore index. In this situation, an access violation occurs. Additionally, an error message that resembles the following is logged in the SQL Server error log, and a dump file is generated:
Date Time spid # Using 'dbghelp.dll' version '4.0.5'Date Time spid # ***Stack Dump being sent to Drive:\Data1\MSSQL\MSSQL11.InstanceName\MSSQL\Log\SQLDump0193.txtDate Time spid # SqlDumpExceptionHandler: Process # generated fatal exception c0000005 EXCEPTION_ACCESS_VIOLATION. SQL Server is terminating this process.Date Time spid # * *******************************************************************************Date Time spid # *Date Time spid # * BEGIN STACK DUMP:Date Time spid # * Date Time spid # Date Time spid # *Date Time spid # *Date Time spid # * Exception Address = 000007FEEABDC8E4 Module(UNKNOWN+0000000000000000)Date Time spid # * Exception Code = c0000005 EXCEPTION_ACCESS_VIOLATIONDate Time spid # * Access Violation occurred reading address 0000000D573C6038
Cause
This issue occurs because a truncated hash table persists incorrectly when the data is being read.
Resolution
Cumulative update information
Cumulative update package 1 for SQL Server 2012 Service Pack 1
The fix for this issue was first released in Cumulative Update 1. For more information about how to obtain this cumulative update package for SQL Server 2012 Service Pack 1, click the following article number to view the article in the Microsoft Knowledge Base:
2765331 Cumulative update package 1 for SQL Server 2012 Service Pack 1Note Because the builds are cumulative, each new fix release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2012 fix release. We recommend that you consider applying the most recent fix release that contains this hotfix. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
2772858 The SQL Server 2012 builds that were released after SQL Server 2012 Service Pack 1 was released
Cumulative update package 3 for SQL Server 2012
The fix for this issue was first released in Cumulative Update 3. For more information about how to obtain this cumulative update package for SQL Server 2012, click the following article number to view the article in the Microsoft Knowledge Base:
2723749 Cumulative update 3 for SQL Server 2012Note Because the builds are cumulative, each new fix release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2012 fix release. We recommend that you consider applying the most recent fix release that contains this hotfix. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
2692828 The SQL Server 2012 builds that were released after SQL Server 2012 was released
Status
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
