We have a SQL Azure database with a large indexed view that supports a website with high traffic during business hours. One of our goals from a DevOps perspective to be able to ship software (including database changes) during business hours without customer impact (i.e., zero-down deployments). We've been able to do this successfully in nearly all areas of our database using compatibility techniques however we run into issues when it comes to including new columns into our Indexed (Materialized) Views in SQL Azure.
I'm looking for general guidance, experience, or unique techniques that would allow for the inclusion of new columns into a fairly large Indexed View without customer impact.
If needed I can provide more specifics but given that we may deal with more indexed views in the future, hoping someone has a couple patterns in mind to consider.
TL;DR; - What is the best way to deal with indexed view changes while maintaining high service availability?