Automatic ApplyMigrations at startup is convenient but scary for lock-heavy tables. Do you run migrations as a deploy step, or trust EF's startup migration?