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,109 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
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,924 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
88 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
111 reads
Today Steve talks about deployments and whether you should roll forward or roll back.
2026-03-04
214 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
153 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,016 reads
A RAG pipeline that answers questions in the demo is not the same thing...
By Steve Jones
“A multitude of bad ideas is necessary for one good idea” – from Excellent...
Yesterday I gave a talk for MSSQLTips called “Building a DBA Agent for Your...
Comments posted to this topic are about the item Adding new column with DEFAULT
I've got a web application for my side business. I've added a SQL Server...
Comments posted to this topic are about the item Looking for New Blood
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