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-10
1,161 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-05-20
752 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
2,012 reads
Acting with confidence is great, but how do you decide when there are potential impacts and concerns about your actions? Steve has a few thoughts today.
2026-04-10
98 reads
Many organizations haven't standardized the way they deploy code to databases, even when they do so for applications. Steve has a few thoughts on this today.
2026-03-13
122 reads
Today Steve talks about deployments and whether you should roll forward or roll back.
2026-03-04
237 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
172 reads
Could you spare 3 minutes to do us a quick favor? Redgate’s running this short survey on how our readers develop and deploy databases. It’s just 12 multiple choice questions, so if you’ve got a couple of minutes to spare, we’d love to hear from you.
2015-02-26 (first published: 2015-02-05)
17,327 reads
When a project is completed, one of the next steps is to roll this project out to the production environment. However a good rollback process is important to ensure that you can remove those changes if there are problems. Longtime author David Poole talks about how he handles this.
2008-10-22
4,037 reads
By James Serra
Making Data AI-Ready, Part 3 (This is the final article in a three-part series...
By Steve Jones
I use ConEmu for my terminal interface. I’m still on Windows 10 at home,...
Creating a Fabric workspace takes about 30 seconds. Restructuring workspaces after people have built...
Comments posted to this topic are about the item Adding new column with DEFAULT...
Comments posted to this topic are about the item Advanced Deployment Scenarios: Stairway to...
Comments posted to this topic are about the item You Need a DBA Pipeline
Which number did the two COUNT(*) return:
DROP TABLE IF EXISTS #tmp CREATE TABLE #tmp (id INT NOT NULL) INSERT INTO #tmp (id) SELECT gs.value FROM GENERATE_SERIES(1, 5) AS gs ALTER TABLE #tmp ADD my_value INT NOT NULL CONSTRAINT df_tmp_my_value DEFAULT 1 SELECT COUNT(*) FROM #tmp AS t WHERE my_value = 1 ALTER TABLE #tmp DROP CONSTRAINT df_tmp_my_value ALTER TABLE #tmp ADD CONSTRAINT df_tmp_my_value DEFAULT 2 FOR my_value SELECT COUNT(*) FROM #tmp AS t WHERE my_value = 1See possible answers
