Welcome to Software Development on Codidact!
Will you help us build our independent community of developers helping developers? We're small and trying to grow. We welcome questions about all aspects of software development, from design to code to QA and more. Got questions? Got answers? Got code you'd like someone to review? Please join us.
Post History
Migrations are applied during the application startup (initialization) only when the application is not accessible yet. One way to go is to leave the existing user as it is and define a designated ...
Answer
#1: Initial revision
by
Alexei
·
2020-11-18T07:42:49Z (about 4 years ago)
Migrations are applied during the application startup (initialization) only when the application is not accessible yet. One way to go is to leave the existing user as it is and define a designated one for the migrations.
Applying [the migrations requires powerful roles](https://stackoverflow.com/a/29831034/2780791) (create or drop table):
- db_datareader
- db_datawriter
- db_ddladmin
The code should like the following:
var optionsBuilder = new DbContextOptionsBuilder<MyContext>();
optionsBuilder.UseSqlServer(
configuration.GetConnectionString("MigrationsConnection"));
var context = new MyContext(optionsBuilder.Options);
await context.Database.MigrateAsync();