In Memory OLTP with Hekaton Engine
•Descargar como PPTX, PDF•
1 recomendación•773 vistas
Hekaton is Microsoft SQL Server's in-memory OLTP engine. It allows for creating memory-optimized tables to fully leverage RAM and provide faster performance than disk-based tables. Memory-optimized tables use new row formats and indexing structures like hash and range indexes that are optimized for memory. Stored procedures can be natively compiled for maximum speed when operating on memory-optimized tables. There are some limitations around data types and features supported. Diagnostic objects like DMVs provide visibility into Hekaton's memory usage and performance.
Recomendados
Recomendados
Más contenido relacionado
La actualidad más candente
La actualidad más candente (20)
Similar a In Memory OLTP with Hekaton Engine
Similar a In Memory OLTP with Hekaton Engine (20)
Más de ITProceed
Más de ITProceed (20)
Último
Último (20)
In Memory OLTP with Hekaton Engine
- 1. In Memory OLTP SQL server 2014 Hekaton Engine Frederik Bogaerts
- 2. Give me more
- 4. Hekaton in a nutshell Please Explain Why Demo
- 5. So long …
- 6. Hekaton – In Memory OLTP
- 8. Prepare your database Create Database Add memory optimized filegroup Add file to filegroup
- 9. Memory Optimized Tables CREATE TABLE [Customer]( [CustomerID] INT NOT NULL PRIMARY KEY NONCLUSTERED HASH WITH (BUCKET_COUNT = 1000000), [Name] NVARCHAR(250) NOT NULL, [CustomerSince] DATETIME NULL INDEX [ICustomerSince] NONCLUSTERED ) WITH (MEMORY_OPTIMIZED = ON, DURABILITY = SCHEMA_AND_DATA);
- 10. Limitations No DML no LOBs, no XML and no CLR data types No Foreign Key or Check constraints No UNIQUE indexes other than PK Max 8 indexes
- 11. Data Structures New Row Format Versioning : Timestamps No data page containers Row header Payload (table columns) Begin Ts End Ts StmtId IdxLinkCount 8 bytes 8 bytes 4 bytes 2 + 2 (padding) bytes 8 bytes * (IdxLinkCount) Source: Microsoft.com
- 15. Natively Compiled Procs CREATE PROCEDURE [dbo].[InsertOrder] @id INT, @date DATETIME WITH NATIVE_COMPILATION, SCHEMABINDING, EXECUTE AS OWNER AS BEGIN ATOMIC WITH (TRANSACTION ISOLATION LEVEL = SNAPSHOT, LANGUAGE = N'us_english') -- insert T-SQL here END
- 16. Limitations Only In MEM tables No OUTER JOIN, no DISTINCT no OR, no subqueries, no CASE Limited built-in functions BUT: Fastest way! Good news : Interface will be expanded in next version
- 17. T-SQL (Not) Supported INTEROP Truncate Dynamic en keyset cursors Cross database Linked servers Locking Hints – Isolation Levels Merge
- 19. Diagnostics All starting with sys.dm_db_xtpDMO •sys.dm_db_xtp_checkpoint_files •sys.dm_db_xtp_table_memory_stats •Sys.dm_db_xtp_index_stats XEvents •From SYS.dm_xe_objects O JOIN SYS.dm.xe_packages P on O.package_guid = P.guid where P.name = ‘XtpEngine’ Perfomance Counters •From sys.dm_os_performance_counters where object_name like ‘XTP%’
- 20. Keep In Mind Data in memory at all times Still using log files Do not exceed 256 GB of InMem table
- 21. Going For Gold
- 24. Follow Technet Belgium @technetbelux Subscribe to the TechNet newsletter aka.ms/benews Be the first to know
- 25. A SQL query walks into a bar and sees two tables. He walks up to them and says 'Can I join you? The SQL query found the table by doing a full scan of the other tables… In the meanwhile, the waitress arrived at the table. Woohoow what a nice view…
- 26. Thank You!
- 27. Belgium’s biggest IT PRO Conference
Notas del editor
- http://msdn.microsoft.com/en-us/library/dn720242.aspx
- As always with new technology, there are new concepts introduced. Throughout my session I’ll talk about these topics one by one.
- Kicks in after a couple of minutes.
- There are also addons done to the SYS.tables, here we can check whether we are dealing with In memory tables and the durability level of the