database deployment

Stairway icons Database Deployments

Concurrency and Baseline Control: Level 5 of the Stairway to Reliable Database Deployments

  • Stairway Step

As database development scales across multiple contributors, concurrency becomes an inherent aspect of the process. Changes that are individually correct may still conflict when developed against a shifting baseline. This level introduces a disciplined approach to managing parallel changesets by controlling their scope, identifying overlap, and resolving conflicts through realignment. By ensuring that only one changeset retains its original baseline while others are adapted accordingly, deployments remain predictable and consistent. Once released, changesets are treated as immutable, and further evolution proceeds through new, forward-only changes.

You rated this post out of 5. Change rating

2026-06-24

1,056 reads

Stairway icons Database Deployments

Stairway to Reliable Database Deployments Level 4 – Preparing for Production Deployment

  • Stairway Step

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.

You rated this post out of 5. Change rating

2026-06-11 (first published: )

1,042 reads

Stairway icons Database Deployments

Stairway to Reliable Database Deployment Level 3 – Rehearsing Changesets Across Environments

  • Stairway Step

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.

You rated this post out of 5. Change rating

2026-06-11 (first published: )

658 reads

Stairway icons Database Deployments

Stairway to Reliable Database Deployments Level 2 - Defining the Deployment Contract

  • Stairway Step

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.

You rated this post out of 5. Change rating

2026-06-11 (first published: )

1,154 reads

Blogs

Introducing azsql-migration-test: Test and Validate Azure SQL Database Migrations

By

Introducing azsql-migration-test, a small open-source CLI that validates your Azure SQL Database migrations against...

Rambling about Data on Wheels – origins, branding, expansion

By

I have been asked many times about how the name “Data on Wheels” came...

Think Twice Before Enabling Fabric’s Inbound Network Protection

By

Fabric inbound network protection involves two tenant-level controls: Private Link and Block Public Internet...

Read the latest Blogs

Forums

Make It Routine

By Steve Jones - SSC Editor

Comments posted to this topic are about the item Make It Routine

DBCC CHECKDB Limits III

By Steve Jones - SSC Editor

Comments posted to this topic are about the item DBCC CHECKDB Limits III

CROSS APPLY Fundamentals: Part 1

By Imran2629

Comments posted to this topic are about the item CROSS APPLY Fundamentals: Part 1

Visit the forum

Question of the Day

DBCC CHECKDB Limits III

On SQL Server 2025, does DBCC CHECKDB support Memory-Optimized tables?

See possible answers