title: Azure Web App deployment slots with database migration
body: <p>I'm currently running a webApp with several deployment slots (e.g. dev, staging, production). Every Slot is connected to a database (db_dev, db_staging, db_production). I want to deploy to the staging slot and then switch with production. How do database migrations fit in here?</p>
  
  <p>I mean, if i deploy a new build with db migrations to staging the db_staging gets updated. What happens if I switch the slots? Do the migrations get applied to db_production? What about downtimes? </p>
  
  <p>From my understanding only the URLs are switched, so after the switch the app in the staging slot would point to the db_production? That does not make sense.</p>
  
  <p>I could deploy to the staging slot and point to db_production (with migrations), but then the db would be updated and could possibly break the app in the live slot.</p>