SYSTEM_VERSIONING is not turned on for a table in a database that has the READ_COMMITTED_SNAPSHOT isolation level enabled in SQL Server 2016

Symptoms

You try to turn on SYSTEM_VERSIONING for a memory-optimized table in a database that has the READ_COMMITTED_SNAPSHOT isolation level enabled. If the DATA_CONSISTENCY_CHECK is not disabled, you may receive an error message that resembles the following:
Msg 41359, Level 16, State 0, Line 36A query that accesses memory optimized tables using the READ COMMITTED isolation level, cannot access disk based tables when the database option READ_COMMITTED_SNAPSHOT is set to ON. Provide a supported isolation level for the memory optimized table using a table hint, such as WITH (SNAPSHOT).

Resolution

The fix for this issue is included in the following cumulative update for SQL Server:


About cumulative updates for SQL Server
About cumulative updates for SQL Server

Workaround

To work around this issue, turn off the data consistency check by adding the DATA_CONSISTENCY_CHECK = OFF clause in your CREATE TABLE statement.

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 Microsoft uses to describe software updates.
Propriedades

ID do Artigo: 3174711 - Última Revisão: 25/07/2016 - Revisão: 1

Comentários