| title | description | author | ms.author | ms.date | ms.service | ms.subservice | ms.topic | monikerRange |
|---|---|---|---|---|---|---|---|---|
Transact-SQL Support for In-Memory OLTP |
Learn about Transact-SQL statements that include syntax options to support In-Memory OLTP. Use links to additional references about supported features. |
MikeRayMSFT |
mikeray |
03/16/2017 |
sql |
in-memory-oltp |
conceptual |
=azuresqldb-current||>=sql-server-2016||>=sql-server-linux-2017||=azuresqldb-mi-current |
[!INCLUDE SQL Server Azure SQL Database Azure SQL Managed Instance]
The following [!INCLUDEtsql] statements include syntax options to support In-Memory OLTP:
-
ALTER DATABASE File and Filegroup Options (Transact-SQL) (added MEMORY_OPTIMIZED_DATA)
-
CREATE DATABASE (SQL Server Transact-SQL) (added MEMORY_OPTIMIZED_DATA)
-
DECLARE @local_variable (Transact-SQL)
In a natively compiled stored procedure, you can declare a variable as NOT NULL. You cannot do so in a regular stored procedure.
AUTO_UPDATE_STATISTICS can be ON for memory-optimized tables, starting with SQL Server 2016. For more information, see sp_autostats (Transact-SQL).
SET STATISTICS XML (Transact-SQL) ON is not supported for natively compiled stored procedures.
For information on unsupported features, see Transact-SQL Constructs Not Supported by In-Memory OLTP.
For information about supported constructs in and on natively compiled stored procedures, see Supported Features for Natively Compiled T-SQL Modules and Supported DDL for Natively Compiled T-SQL modules.
In-Memory OLTP (In-Memory Optimization)
Migration Issues for Natively Compiled Stored Procedures
Unsupported SQL Server Features for In-Memory OLTP
Natively Compiled Stored Procedures