change management

Technical Article

Stairway to Reliable Database Deployments Level 6 – Managing Changesets Over Time

  • Stairway Step

As database changesets accumulate over time, they gradually become more than deployment artifacts. This level explores how a well-organized changeset library evolves into a replayable representation of the database’s structural history, supporting not only reliable deployments but also reconstruction, auditing, and long-term maintainability. Through practical examples and a real-world case study, it shows why maintaining coherent Create and Rollback scripts continues to provide value long after a successful production deployment.

★ ★ ★ ★ ★ ★ ★ ★ ★ ★

You rated this post out of 5. Change rating

2026-08-05

573 reads

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,103 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,185 reads

Blogs

Take Time to Gain Perspective

By

Probably the best piece of advice I ever received is to take time to...

The Fringe Festival

By

I was lucky enough to take a vacation a decade ago in Edinburgh with...

Demo for Parameter Sniffing and Memory Grant Feedback

By

Disclaimer: The following is built with Claude Code. Just need to justify my $100/mo...

Read the latest Blogs

Forums

Learn From History

By Grant Fritchey

Comments posted to this topic are about the item Learn From History

The SQL Server MCP Server

By Steve Jones - SSC Editor

Comments posted to this topic are about the item The SQL Server MCP Server

The Hidden Danger of Wildcard Operators In Join Operations

By sabyda

Comments posted to this topic are about the item The Hidden Danger of Wildcard...

Visit the forum

Question of the Day

The SQL Server MCP Server

How do I get an MCP server for my SQL Server 2025 database from Microsoft?

See possible answers