Entity Framework Core, code first, makes it easy for developers to work with a database using C# objects and it includes handy automatic generated migrations, but…
DBAs aren't always that happy with these automatic ‘out-of-their-control’ migrations.

We database people want to know what has changed upfront and want to review a migration before it hits any environment. We prefer a more database code engineered approach, with tools like Flyway. Since the development team already chose EF Core code-first and you don't want to repeat the work, it looks like you're stuck with EF Core.

What if, I tell you that these ways of working aren't mutually exclusive?
That we can get these migrations in harmony by converting them, manually or in a pipeline.
So, we can start the database development in EF Core, but reviewing the changes and releasing it into other environments is controlled by the database team with the help of Flyway.

Do you want to know how to have it both ways and experience the benefits like; faster deployment time, increased collaboration between software developers and DBAs and improved overall quality of database deployments?
Please come to my session!

The target audience includes:
- Database Administrators (DBAs) concerned with migration control.
- IT Project Managers and Team Leads overseeing software and database teams
- Software Developers using C# and Entity Framework Core.