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
Each new cumulative update for SQL Server contains all the hotfixes and all the security fixes that were included with the previous cumulative update. Check out the latest cumulative updates for SQL Server:
Service pack information for SQL Server 2016
This problem is fixed in the following service pack for SQL Server:
Service packs are cumulative. Each new service pack contains all the fixes that are in previous service packs, together with any new fixes. We recommend that you apply the latest service pack and the latest cumulative update for that service pack. You do not have to install a previous service pack before you install the latest service pack. Use Table 1 in the following article to find more information about the latest service pack and latest cumulative update:
Determine the version, edition, and update level of SQL Server and its components
References
Learn about the terminology that Microsoft uses to describe software updates.
