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,111 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)
721 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,220 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)
371 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,930 reads
Today Steve talks about the concept of what a failure is when deploying changes.
2025-06-13
87 reads
This guide will walk you through the process of deploy DACPAC to Azure SQL database directly from Visual Studio.
2025-03-10
1,838 reads
If you build software for customers, you have a pipeline. It might not be good, but you have one. Steve recommends you work to make sure this is a repeatable, reliable pipeline.
2023-10-13
154 reads
You’ve got an existing application with a database back end. You’re thinking about changing the database, and you don’t wanna break stuff.
2023-07-28
You want to use SQL Compare or SQL Change Automation (SCA) to create or update a database, and at the same time ensure that its data is as you expect. You want to avoid running any additional PowerShell scripting every time you do it, and you want to keep everything in source control, including the data. You just want to keep everything simple. Phil Factor demonstrates how it's done, by generating MERGE scripts from a stored procedure.
2019-12-13
By Steve Jones
It’s time for T-SQL Tuesday again and this is a great prompt to start...
By alevyinroc
T-SQL Tuesday is a monthly blog party hosted by a different community member each...
How I used AI for this postChatGPT to generate images based on info specifically...
Telp/Wa 62 821-8200-233 Jl. H. R. Rasuna Said No.Kav. 01, RW.6, Guntur, Kecamatan Setiabudi,...
Telp/Wa 62 821-8200-203 Koperasi Sejati Mulia, Jl. Raya Ragunan B 1, RT.3/RW.3, Jati Padang,...
Telp/Wa 62 821-8200-174 Gd. Graha Inti Fauzi, Jl. Buncit Raya No.22 Lt. Dasar, RT.2/RW.7,...
Which number will the COUNT() return after executing the following statements:
DROP TABLE IF EXISTS #test; CREATE TABLE #test (id INT) INSERT INTO #test (id) SELECT * FROM GENERATE_SERIES(1, 3) AS gs ; ALTER TABLE #test ADD flag BIT CONSTRAINT DF_#test_flag DEFAULT 0; go UPDATE #test SET flag = 0 WHERE id = 1 UPDATE #test SET flag = 1 WHERE id = 2 INSERT INTO #test (id) VALUES (4) SELECT COUNT(*) FROM #test AS t WHERE flag = 0See possible answers