Operational Defect Database
BugZero found this defect 1308 days ago.
Data sources
All data on this page is proprietary to BugZero® or gathered from public sources
Microsoft SQL Server | 11983956
KB4131960 - FIX: Access violation when you run a nested select query against a columnstore index in SQL Server - Microsoft Support
Last update date:
7/19/2023
Affected products:
SQL Server 2017 on Windows (all editions)
SQL Server 2016 Developer - duplicate (do not use)
SQL Server 2016 Enterprise - duplicate (do not use)
SQL Server 2016 Enterprise Core - duplicate (do not use)
SQL Server 2016 Standard - duplicate (do not use)
Affected releases:
build lower than 14.0.3029.16
Fixed releases:
14.0.3029.16
Description:
Symptoms
Assume that you use a columnstore index in Microsoft SQL Server 2016. When you run a nested select query against the columnstore index, an access violation might occur. Additionally, an error message that resembles the following is logged in the SQL Server error log file: date time Server Error: 17310, Severity: 20, State: 1.date time Server A user request from the session with SPID 55 generated a fatal exception. SQL Server is terminating this session. Contact Product Support Services with the dump produced in the log directory.date time spid55 ***Stack Dump being sent to C:\Program Files\Microsoft SQL Server\MSSQL13.MSSQLSERVER\MSSQL\LOG\SQLDump0053.txtdate time spid55 SqlDumpExceptionHandler: Process 55 generated fatal exception c0000005 EXCEPTION_ACCESS_VIOLATION. SQL Server is terminating this process.date time spid55 * *******************************************************************************date time spid55 *date time spid55 * BEGIN STACK DUMP:date time spid55 * date time spid 55date time spid55 *date time spid55 *date time spid55 * Exception Address = 00007FFCBBD008A4 Module(sqlmin+0000000000E608A4)date time spid55 * Exception Code = c0000005 EXCEPTION_ACCESS_VIOLATIONdate time spid55 * Access Violation occurred writing address 0000000000000000
Resolution
The fix for this problem is included in the following updates: Cumulative Update 8 for SQL Server 2017 Cumulative Update 1 for SQL Server 2016 Service Pack 2 Cumulative Update 9 for SQL Server 2016 Service Pack 1
About SQL Server builds
Each new build for SQL Server contains all the hotfixes and security fixes that were in the previous build. We recommend that you install the latest build for your version of SQL Server: The latest build for SQL Server 2017 The latest build for SQL Server 2016
Status
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
References
Learn about the terminology that Microsoft uses to describe software updates.
