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,222 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
816 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,132 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
112 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
140 reads
Today Steve talks about deployments and whether you should roll forward or roll back.
2026-03-04
284 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
189 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,060 reads
This month’s blogging party is hosted by Jeff Ianucci – his challenge is to...
As for me, I'll keep writing whenever time permits. I don't expect every post...
By Steve Jones
This is an interesting invitation this month. Jeff Ianucci is a new host, and...
Comments posted to this topic are about the item Pay for Performance, which is...
Jl. Raya R.Dengklok No.27, RT.049/RW.011, R.Dengklok Sel., Kec. R.Dengklok, Karawang, Jawa Barat 41352
Comments posted to this topic are about the item Switching Schemas I
I run this query:
SELECT s.name AS schemaname , o.name AS objectname FROM sys.objects o INNER JOIN sys.schemas s ON s.schema_id = o.schema_id WHERE o.name = 'Beer'I get one row back for an object named dbo.beer. There is an ETL schema and both of these are nonpartitioned tables. I run this code:
ALTER TABLE dbo.beer switch TO etl.beerWhat happens? See possible answers