How Can I Achieve Zero-Downtime Database Deployments with a Blue-Green Strategy?

Breaking replication to deploy might seem counterintuitive if you want zero downtime. A good approach is to set up a read replica as your ‘green’ environment. Deploy the changes there and test them out before switching over. Azure SQL even has failover groups to help with this. Just avoid breaking replication mid-deployment unless you're ready for a tough chat with your manager! If your new changes are just schema updates, consider using online migrations or feature flags so the live database stays unaffected.

You might want to look into using Liquibase for database migrations. It’s a solid tool for rolling out changes seamlessly.

Have you thought about using tools like Flyway for managing database migrations? It could help streamline your deployment process.