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-05-20
404 reads
Learn about restoring your keys from an Azure Key Vault in the event of a DR situation.
2026-05-13
1,069 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-05-06
703 reads
In this level we learn how to ensure our keys are backed up to the Azure Key Vault for safekeeping.
2026-04-22
692 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-04-15
66 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-04-15
1,452 reads
Learn how backup and restore work in Azure SQL Hyperscale in this next level in the stairway series.
2025-12-17
834 reads
In this level, we learn about the database file size growth in Hyperscale.
2025-12-03
103 reads
Learn about how the Log Service helps manage transactions in the Hyperscale Tier.
2025-10-29
1,096 reads
In Level 2 of the Stairway to Hyperscale, we learn about Page Servers in more detail.
2025-09-17
861 reads
By James Serra
What problem is Fabric Ontology trying to solve? For years, most data conversations have...
By Steve Jones
Recently I ran across some code that used a lot of QUOTENAME() calls. A...
By ChrisJenkins
There are some telltale signs that your growing business has outgrown Excel for your...
Jl. Yos Sudarso Pantai No.08, Karang Rejo, Kec. Tarakan Bar., Kota Tarakan, Kalimantan Utara...
Tlp/Wa_Cs:0817-866-887 Jl. Komp. Rs. Fatmawati No.1, RT.1/RW.9, Cilandak Bar., Kec. Cilandak, Kota Jakarta Selatan,...
Tlp/Wa_Cs:0817-866-887 Jl. Danau Sunter Utara Jalan Kavling No.3 Blok A, RT.2/RW.18, Sunter Agung, Kec....
When I use QUOTENAME(), I can optionally provide the character used to surround the string in the result. Can I use any character?
See possible answers