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,212 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
806 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,121 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
111 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
139 reads
Today Steve talks about deployments and whether you should roll forward or roll back.
2026-03-04
272 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
188 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,059 reads
By Brian Kelley
During COVID, I attended training on software/enterprise architecture given by Mark Richards. One of...
For me, the objective is straightforward: have a backup strategy that is reliable, understandable,...
By DesertDBA
Note: This post is the invitation for T-SQL Tuesday #204 on November 3rd, 2026....
Comments posted to this topic are about the item The ##MS_DatabaseConnector## User
Comments posted to this topic are about the item Planning for Change
Comments posted to this topic are about the item Importing Excel files into SQL...
On SQL Server 2025, I run this code as a sysadmin:
CREATE LOGIN Demo WITH PASSWORD = 'Demo1234567' GO ALTER SERVER ROLE ##MS_DatabaseConnector## ADD MEMBER Demo GOI then login as Demo and run this:
USE sandbox go SELECT CURRENT_USERWhat is returned? See possible answers
