Skip to content

Latest commit

 

History

History
37 lines (30 loc) · 2.16 KB

mssqlserver-41368-database-engine-error.md

File metadata and controls

37 lines (30 loc) · 2.16 KB
title description author ms.author ms.date ms.service ms.subservice ms.topic helpviewer_keywords
MSSQLSERVER_41368
MSSQLSERVER_41368
MashaMSFT
mathoma
05/25/2022
sql
supportability
reference
41368 (Database Engine error)

MSSQLSERVER_41368

[!INCLUDE SQL Server]

Details

Attribute Value
Product Name [!INCLUDEssNoVersion]
Event ID 41368
Event Source MSSQLSERVER
Component SQLEngine
Symbolic Name SQL_IMPLICIT_AND_EXPLICIT_TX_NOT_SUPPORTED
Message Text Accessing memory optimized tables using the READ COMMITTED isolation level is supported only for autocommit transactions. It is not supported for explicit or implicit transactions. Provide a supported isolation level for the memory optimized table using a table hint, such as WITH (SNAPSHOT).

Explanation

Accessing memory-optimized tables using the READ COMMITTED isolation level is supported only for autocommit transactions. For more information, see Transactions with In-Memory Tables and Procedures.

When accessing a memory-optimized table from an explicit transaction that was started with BEGIN TRANSACTION, or from an implicit transaction, if IMPLICIT_TRANSACTIONS is set to ON, the READ COMMITTED isolation level is not supported.

User Action

When accessing a memory-optimized table from an explicit or implicit READ COMMITTED transaction, use SNAPSHOT to access the table. This can be achieved by using the table hint WITH (SNAPSHOT) (for more information, see Transactions with In-Memory Tables and Procedures) or by setting the database option MEMORY_OPTIMIZED_ELEVATE_TO_SNAPSHOT to ON (for more information, see ALTER DATABASE SET Options (Transact-SQL)).

See Also

In-Memory OLTP (In-Memory Optimization)