This level examines how a rehearsed changeset is transformed into production-ready deployment artifacts. By consolidating scripts into controlled execution units and validating the resulting artifacts, the approach ensures that production deployment remains predictable and aligned with what was proven during rehearsal.
2026-06-11 (first published: 2026-06-10)
1,061 reads
After defining the deployment contract in the previous level, this article focuses on validating a changeset before it reaches production. Rehearsal across environments ensures that execution order, rollback behavior, and baseline alignment all behave exactly as expected.
2026-06-11 (first published: 2026-05-20)
668 reads
Learn about restoring your keys from an Azure Key Vault in the event of a DR situation.
2026-05-13
1,254 reads
Level 2 formalizes the behavioral guarantees that a changeset must provide in order to be safely deployed and rolled back. It introduces the deployment contract, checkpoint semantics, and the structural scope of Create and Rollback scripts. Data changes are addressed through a dedicated Update mechanism, with clear boundaries and limitations. By the end of this level, a changeset becomes a predictable and well-defined unit that can be reasoned about independently of execution context.
2026-06-11 (first published: 2026-05-06)
1,175 reads
In this level we learn how to ensure our keys are backed up to the Azure Key Vault for safekeeping.
2026-04-22
732 reads
This stairway addresses many of the issues that come about with ad hoc database deployment processes in many organizations. You will learn how to better architect and structure your processes to ensure a reliable database deployment for your applications.
2026-06-11 (first published: 2026-04-15)
265 reads
Stairway to Reliable Database Deployments introduces a progressive approach to managing database changes with clear intent, predictable rollback, and explicit behavioral guarantees. Starting from change design and moving toward execution and coordination in complex environments, the Stairway provides a conceptual framework for deploying database changes safely and consistently, independent of specific tools or automation platforms.
2026-06-11 (first published: 2026-04-15)
1,780 reads
Learn how backup and restore work in Azure SQL Hyperscale in this next level in the stairway series.
2025-12-17
879 reads
In this level, we learn about the database file size growth in Hyperscale.
2025-12-03
123 reads
Learn about how the Log Service helps manage transactions in the Hyperscale Tier.
2025-10-29
1,118 reads
A nightly load into sales_fact fails. Ask an orchestrating agent to break down the...
By Steve Jones
It’s been some time since I provided a car update, so I decided to...
By James Serra
An architecture scenario Imagine separate Sales, Finance, Shared Data, and Executive Analytics workspaces. Sales...
I have a really stupid question... Is there an easy way to search for...
Comments posted to this topic are about the item How to Work with On-Premises...
Comments posted to this topic are about the item Escaping Strings
The STRING_ESCAPE() function requires 2 parameters in SQL Server 2025. The first is a string of text and the second is the type of escape rules being used. What are the options for the second parameter?
See possible answers