2024-10-09
315 reads
In-Memory OLTP Tables
2024-10-02
398 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
997 reads
2016-10-06
1,039 reads
Blogs
Upgrading SQL Server Containers on the Laptop
By Steve Jones
I don’t have SQL Server installed on my laptop. In an effort to keep...
How to Find Expensive Queries in Amazon Redshift
Slow-running queries can degrade your Redshift cluster’s performance and lead to increased costs. Identifying...
The Notification Trap: How Input Fatigue Is Killing Deep Work in Tech
By gbargsley
If you've been here before, you know this blog is usually about SQL Server,...
Forums
SQL 2019 instance with AG, across 2 Windows 2016 OS servers - OSin-place upgrade
Hi all Can I get some perspective from the community please on performing in-place...
How Long is a Long I/O?
Comments posted to this topic are about the item How Long is a Long...
T-SQL Trigonometric Functions in SQL Server
Comments posted to this topic are about the item T-SQL Trigonometric Functions in SQL...
Question of the Day
How Long is a Long I/O?
In SQL Server 2025, a long I/O is recorded in the error log with message 833. How long much an I/O request be outstanding before this message is written to the log?
See possible answers