What are In-Memory OLTP and Memory Optimized Tables

In-Memory OLTP

In-Memory OLTP is an in-memory computing technology developed by Microsoft to speedup the performance of transaction processing applications running on SQL Server databases. In-Memory OLTP is built with two core components: memory-optimized tables and natively compiled stored procedures. In-Memory OLTP, also known as 'Hekaton' and 'In-Memory Optimization', which is Microsoft's latest in-memory processing technology of 2014.

In-Memory Tables

It is integrated into SQL Server's Database Engine and which can be used in the similar way as other Database Engine component. In-Memory OLTP originally came with SQL Server 2014 .

Memory-Optimized Tables

Memory-optimized tables are fully durable, like transactions on disk-based tables, transactions on memory-optimized tables are fully ACID compatible . Memory-optimized tables and natively compiled stored procedures support only a subset of Transact-SQL features.

The primary storage for memory-optimized tables is the RAM. Rows in the table are read from and written to memory. A second copy of the table data is maintained on disk, but only for durability purposes.

Thanks for reading

Plz dont forget to like Facebook Page..

https://www.facebook.com/pages/Sql-DBAcoin/523110684456757

Comments

History of MySQL from AB Corp to Cloud Database

MySQL was created by a Swedish company, MySQL AB, founded by David Axmark, Allan Larsson and Michael "Monty" Widenius. Original development of MySQL by Widenius and Axmark began in 1994. The first version of MySQL appeared on 23 May 1995. Its name is a combination of "My", the name of co-founder Michael Widenius's daughter,and "SQL", the abbreviation for Structured Query Language. · 23 May 1995 - First internal release · Year 1996 - Version 3 o Simple CRUD operations o January 1997 Windows version was released on 8 January 1998 for Windows 95 and NT o production release 1998, from www.mysql.com · Year 2002 - Version 4 o MyISAM o unions o Tracking o B-trees o s...

Configure Impersonation Authentication in IIS8 for MVC Application

Impersonation is when ASP.NET executes code in the context of an authenticated and authorized client. By default, ASP.NET does not use impersonation and instead executes all code using the same user account as the ASP.NET process, which is typically the ASPNET account. There are 5 below steps by which we can establish Impersonation configuration in our secured application environment. 1.) Creation of Application/Proxy user where Application is hosted. 2.) Give appropriate access to the user. 3.) Create Database Login user on database. 4.) Authenticate User and provide credential on IIS. 5.) Then Configure web.config on Application.

How to add an article in Transactional Replication

If we have a set-up of Transactional Replication for Data Distribution running and wanting to add new object to replication on other server we can follow below process. To add an article In Transaction replication with PUSH Subscription

The Young DBA

Search This Blog