In-Memory OLTP - what's new in SQL2016 CTP3 |
We have been hard at work to add features to In-Memory OLTP to make it easier to build apps and to adopt In-Memory OLTP in existing apps, as well as to increase overall performance and scaling. Below is the list of In-Memory OLTP enhancements that we have released in SQL2016 thus far, up to and including CTP3. There is more to come!
Let us know what you think!
Transact-SQL Improvements:
Disjunction (OR, NOT)
UNION and UNION ALL
SELECT DISTINCT
OUTER JOIN
Subqueries in SELECT statements (EXISTS, IN, scalar subqueries)
Nested execution (EXECUTE) of natively compiled modules
Natively compiled inline table-valued functions (TVFs)
EXECUTE AS CALLER support - the EXECUTE AS clause is no longer required for native modules
Built-in security functions and increased support for built-in math functions
FOREIGN KEY constraints between memory-optimized tables
CHECK constraints
UNIQUE constraints
Triggers (AFTER) for INSERT/UPDATE/DELETE operations. Triggers on memory-optimized tables are natively compiled, and thus use WITH NATIVE_COMPILATION.
The new ALTER TABLE ... ADD/DROP/ALTER INDEX syntax is introduced for index changes on memory-optimized tables
(var)char columns can use any code page supported by SQL Server
Character columns in index keys can use any SQL Server collation
Expressions in natively compiled modules as well as constraints on memory-optimized tables can use any SQL Server collation
Performance and Scaling improvements:
Enhancements in SQL Server Management Studio:
Cross-feature support:
For more information, see In-Memory OLTP (In-Memory Optimization).
Комментировать | « Пред. запись — К дневнику — След. запись » | Страницы: [1] [Новые] |