| title | MSSQLSERVER_41368 | |
|---|---|---|
| description | MSSQLSERVER_41368 | |
| author | MashaMSFT | |
| ms.author | mathoma | |
| ms.date | 05/25/2022 | |
| ms.service | sql | |
| ms.subservice | supportability | |
| ms.topic | reference | |
| helpviewer_keywords |
|
[!INCLUDE SQL Server]
| 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). |
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.
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)).