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 | 11195379
KB4046056 - FIX: Assertion occurs when you access memory-optimized table through MARS in SQL Server 2017 or 2016 - Microsoft Support
Last update date:
9/15/2021
Affected products:
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)
SQL Server 2016 Service Pack 1
SQL Server 2017 Developer on Windows
SQL Server 2017 Enterprise on Windows
SQL Server 2017 Enterprise Core on Windows
SQL Server 2017 Standard on Windows
SQL Server 2016
SQL Server 2016 Service Pack 3 - duplicate (do not use)
Affected releases:
build lower than 14.0.3008.27
Fixed releases:
14.0.3008.27
Description:
Symptoms
Consider the following scenario: You use In-Memory OLTP and Multiple Active Result Sets (MARS) in an instance of Microsoft SQL Server 2017 or 2016. You create a clustered column store index for a memory-optimized table. You connect to the instance of SQL Server by using a MARS-enabled connection. When you run a query to access data from the memory-optimized table, you may notice that an assertion error occurs and the connection is killed. Additionally, a minidump is generated on the server side.
Status
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
Resolution
This problem is fixed in the following cumulative updates for SQL Server: Cumulative Update 2 for SQL Server 2017 Cumulative Update 9 for SQL Server 2016 RTM Cumulative Update 6 for SQL Server 2016 SP1
Service pack information for SQL Server 2016
This problem is fixed in the following service pack for SQL Server: Service Pack 3 for SQL Server 2016
References
Learn about the terminology that Microsoft uses to describe software updates.
