schema deployment

Stairway icons Database Deployments

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

  • 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-10

1,226 reads

Stairway icons Database Deployments

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

  • 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-05-20

822 reads

Blogs

Word to the wise: don’t turn on SQL vulnerability checks on a blog about SQL

By

Recently, in an attempt to thwart leechers (1990s kids will know), I added some...

Dazzling Stuff in Databricks (SQL) – Qualify

By

Once upon a time I had a series about some cool stuff in Snowflake:...

Advice I Like: Overnight Success

By

“Most overnight successes – in fact any significant successes – take at least 5...

Read the latest Blogs

Forums

Why Successful SQL Server Backups Are Not Enough

By Almighty

Comments posted to this topic are about the item Why Successful SQL Server Backups...

Adding Bits II

By Steve Jones - SSC Editor

Comments posted to this topic are about the item Adding Bits II

An Unlimited Token Budget

By Steve Jones - SSC Editor

Comments posted to this topic are about the item An Unlimited Token Budget

Visit the forum

Question of the Day

Adding Bits II

I have a table, dbo.bittest, where I am testing an application response. This has this structure:

CREATE TABLE [dbo].[BitTest]
(
[insertdate] [datetime] NULL CONSTRAINT [DF__BitTest__insertd__300F11AC] DEFAULT (getdate()),
[a] [bit] NULL
) ON [PRIMARY]
GO
My application runs this code:
INSERT dbo.BitTest
(
    insertdate,
    a
)
VALUES
(DEFAULT, true)
GO

See possible answers