Glasses, calculator, tablet, white neat desk

System-versioned ledger tables: things you can’t do

This is the third post in the series about system-versioned ledger tables, a new feature introduced in Azure SQL Database. You can read Part 1 and Part 2 if you haven’t already. Every choice we make is a trade-off. New features have limitations, and ledger tables are no exception. Some of these limitations are perfectly
-> Continue reading System-versioned ledger tables: things you can’t do

Glasses, calculator, tablet, white neat desk

System-versioned ledger tables: the next step

In the first post of this series, we learned about a new type of system-versioned table that also works at the database level and introduces a mechanism that demonstrates whether your database has been tampered with. Very simply, if the cryptographic hash does not match what is in the off-site digest, your database has been
-> Continue reading System-versioned ledger tables: the next step

Glasses, calculator, tablet, white neat desk

Introducing system-versioned ledger tables

As long-time readers of this blog know, I’m a big fan of temporal tables, also known as system-versioned temporal tables. Until recently, temporal tables were synonymous with system-versioned tables, but all that changed a short while ago with the introduction — in Azure SQL Database — of system-versioned ledger tables. This new series of posts
-> Continue reading Introducing system-versioned ledger tables

Azure SQL logo

A summary of new features in Azure SQL Database

It has been some time since I last wrote about Azure SQL Database. Although it has been more than three years since SQL Server 2017 was released, Microsoft have not been resting on their laurels. Here is a list of features in public preview that you can start testing and including in your future plans
-> Continue reading A summary of new features in Azure SQL Database

Post image

Microsoft presents: MySQL and PostgreSQL?

For the longest time, MySQL has been the recommended database platform for blogs and other websites. It’s free. It’s available on every version of Linux, which is the most common web server platform. If you need something more complex but still free, there’s PostgreSQL. But there’s a lot going on beyond that word “free”. Because
-> Continue reading Microsoft presents: MySQL and PostgreSQL?

Post image

A look back, and a look forward

Time flies. My father used to wear a t-shirt that claimed, “When you’re over the hill, you pick up speed.” I’m turning 40 in a few days. I still feel like a teenager in many respects. SQL Server, released in 1989, is 27 years old now. It’s about the same age I was when a
-> Continue reading A look back, and a look forward

Post image

Look, Ma, No Surprises

Last week I demonstrated at least 30% performance improvement by switching to memory optimised table-valued parameters on SQL Server 2016. This week I will demonstrate the same test using Azure SQL Database, on the Premium tier, where In-Memory OLTP is supported. My test harness is the same. I will create a temp table and a
-> Continue reading Look, Ma, No Surprises

Post image

Should I upgrade SQL Server 2012, or migrate to Azure?

[Last updated February 27, 2020] Brent Ozar Unlimited runs a website called SQL Server Updates which comes in really handy for keeping your on-premises SQL Server up to date. Of interest is that extended support for SQL Server 2012 ends on 12 July 2022, just two years from now. As we know, SQL Server 2019
-> Continue reading Should I upgrade SQL Server 2012, or migrate to Azure?

Post image

Temporal Tables in Azure SQL Database

In the latest Microsoft Azure newsletter I received last week was this most excellent news: Azure SQL Database Temporal Tables generally available Temporal Tables let customers track the full history of data changes in Azure SQL Database without custom coding. Customers can focus data analysis on a specific point in time and use a declarative
-> Continue reading Temporal Tables in Azure SQL Database

Post image

Database Throughput Units

Last time we briefly touched on the metric that Microsoft uses to keep your Azure SQL Database in check: the DTU, or database throughput unit. It uses a combination of CPU, I/O and log flushes/second, using a special algorithm, to calculate a single unit. The reason for this is simple: Our databases don’t use the same resources
-> Continue reading Database Throughput Units