2024-10-09
306 reads
In-Memory OLTP Tables
2024-10-02
392 reads
Converting a Database to In-Memory OLTP
In-Memory OLTP was introduced with SQL Server 2014 as a way to improve transaction performance. There are several scenarios that are not supported, such as some data types, and Darko Martinovic describes the issues and provides workarounds. He also has provided a tool to assist in migrating disk-based tables to In-Memory optimized tables.
2018-06-11
3,363 reads
Microsoft IT: A Case Study on “Hekaton” against RPM – SQL Server 2014 CTP1
This paper shares the approach used to understand and determine: 1) Using ‘Hekaton’ in SQL Server 2014 against RPM, including performance analysis. 2)
Understand the specifics involved while migrating to Hekaton.
2017-08-09
3,784 reads
2017-03-24
986 reads
2016-10-06
1,034 reads
Blogs
Query multiple Azure SQL Databases
I was sick of changing context in Azure Data Studio while cleaning up things...
KDA: Echoes of Deception - Case 3
By Zikato
The crime spree in Digitown is not ending. This time 20 cars have been...
The Book of Redgate: Do Your Best Work
By Steve Jones
One of our mission statements in the Book of Redgate says: attempt to do...
Forums
Sustainable Procurement Best Practices for ESG-Driven Supply Chains
In today’s business world, Environmental, Social, and Governance (ESG) criteria are no longer optional. Customers, investors,...
Shining a Light on Shadow AI - Responsible Data Protection When AI is Everywhere
Comments posted to this topic are about the item Shining a Light on Shadow...
CAST(VARCHAR(n)) resolved performance issue?
Hi, I would love to hear if anyone can tell me why a CAST...
Question of the Day
The Internals of Writing a Page
In SQL Server, when the buffer manager write pages to disk, page protection is added to the pages. There are two types of protection: torn page protection and checksum page protection. What happens with regards to concurrency with page protection during writes?
See possible answers