CD Updates With No Downtime
I understand A/B switching of environments for the application side of things, but what strategies can I use to avoid downtime while updating an application relying on MS SQLServer without losing any data? We're currently doing automated deployments with DACPAC's, but there's always some downtime involved with our current deployment model - turn off services, update database, bring services back online. I'd like to get to "anytime" deployments without impacting our customers, but can't figure out a good way to accomplish the database updates.
---
