You’re tired of taking outages to deploy changes to your database schema.
Wouldn’t it be cool to have two different SQL Servers so that you could:
Point your customer traffic at ServerA Apply your deployment scripts to ServerB (which isn’t taking any customer traffic) Point your customer traffic over to the newly deployed ServerB Apply your deployment scripts to ServerA (which isn’t taking any customer traffic)
Presto! All your servers are up to date and in sync, right? Well, no, not in SQL Server at least.
Illustrating the problem with a simple schema change
We’ll use the Posts table in