FIX: Assertion occurs when you access memory-optimized table through MARS in SQL Server 2016 and 2017

Applies to: SQL Server 2016 DeveloperSQL Server 2016 EnterpriseSQL Server 2016 Enterprise Core


Consider the following scenario:

  • You use In-Memory OLTP and Multiple Active Result Sets (MARS) in an instance of Microsoft SQL Server 2016 or 2017.
  • 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.


This issue 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


Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.


Learn about the terminology that Microsoft uses to describe software updates.