Additional Articles


Technical Article

In-Memory OLTP – Common Workload Patterns and Migration Considerations

In-Memory OLTP is a high performance, memory-optimized engine integrated into SQL Server 2014 and designed for modern hardware trends. In-Memory OLTP allows users to move data into memory resident tables while keeping other data in traditional, disk-based table structures. For performance critical workloads, users can also migrate Transact-SQL code to natively compiled stored procedures. This can provide additional performance gains. This paper aims to help readers understand some of the common architectural patterns where In-Memory OLTP has provided significant benefits. The paper also discusses considerations for migrating applications to In-Memory OLTP.

★ ★ ★ ★ ★ ★ ★ ★ ★ ★

You rated this post out of 5. Change rating

2018-06-22

2,677 reads

Technical Article

In-Memory OLTP – SQL Server In-Memory OLTP Internals Overview

In-Memory OLTP (project “Hekaton”) is a new database engine component, fully integrated into SQL Server. It is optimized for OLTP workloads accessing memory resident data. In-Memory OLTP allows OLTP workloads to achieve significant improvements in performance, and reduction in processing time. Tables can be declared as ‘memory optimized’ to enable In-Memory OLTP’s capabilities. Memory-optimized tables are fully transactional and can be accessed using Transact-SQL. Transact-SQL stored procedures can be compiled to machine code for further performance improvements on memory-optimized tables. The engine is designed for high concurrency and blocking is minimal.

★ ★ ★ ★ ★ ★ ★ ★ ★ ★

You rated this post out of 5. Change rating

2018-06-21

2,997 reads

Technical Article

Databases with MAXSIZE Set

Every DBA needs to appropriately manage database growth. No DBA wants an application to fail because the database is out of space. A database can run out of space a number of different ways. One of those ways is to set the MAXSIZE of a database. When the database grows to the MAXSIZE the database will not grow anymore and if someone tries to add more rows they will get an error saying the database is full.

★ ★ ★ ★ ★ ★ ★ ★ ★ ★

You rated this post out of 5. Change rating

2018-06-19

2,410 reads

External Article

Hyper-V and PowerShell: Shielded Virtual Machines

In Windows Server 2016, Microsoft have implemented a strong security concept called Shielded Virtual Machines. Shielded VMs have been improved in the Windows Server 2019 release. In the second part of this series, Nicolas describes what Shielded Virtual Machines are and how to configure them using PowerShell.

2018-06-18

2,979 reads

Blogs

Cleaning Up Azure MS Defender Billing

By

I have a few Azure subscriptions, which are fairly small and not used that...

Installing and Configuring containerd as a Kubernetes Container Runtime

By

This post shows you how to install containerd as the container runtime for Kubernetes...

It’s 2026 and I’m retired, so lets get Visual Basic 6.0 to run on Windows 11

By

In 1999 I released my first commercial software product. ShutOff 2000 was a Windows...

Read the latest Blogs

Forums

SQL Server Vector Support II

By Steve Jones - SSC Editor

Comments posted to this topic are about the item SQL Server Vector Support II

Great Things

By Steve Jones - SSC Editor

Comments posted to this topic are about the item Great Things

Troubleshooting Slow Queries That Already Have an Index

By Imran2629

Comments posted to this topic are about the item Troubleshooting Slow Queries That Already...

Visit the forum

Question of the Day

SQL Server Vector Support II

With regard to SQL Server 2025's Vector support, what is an embedding?

See possible answers