Without migration, model and schema changes pushed

Ruchi Sharavat

We had generated 1 Code First Approach migration in develop branch but suddenly got a requirement to do partial schema changes on production. Steps follwowed:

1. Modified schema directly on production DB(multiple databases)

2. Pushed just Model schema changes

3. No migration snapshots created or pushed

This process didn't create any problem on most of the databases while accesses from UI but for some it was throwing this error while accessing from UI:

Unable to update database to match the current model because there are pending changes and automatic migration is disabled. Either write the pending model changes to a code-based migration or enable automatic migration. Set DbMigrationsConfiguration.AutomaticMigrationsEnabled to true to enable automatic migration.

Want to know why error is for few databases and not for all.

4 Replies

Know the answer? Post it — somebody with the same question will find it here.

Ruchi Sharavat4y ago
All have same number of migration in _migrationhistory
Sachin Singh4y ago
there will be no migration history (_migrationFolder) folder on all those databases where it worked.
Ruchi Sharavat4y ago
Hi Sachin,

The problem is, i have not generated migration. I just updated the model and did schema changes in db directly. I do have multiple databases with same schema, I did manual DB changes in all of them but application worked fine while executed against some databases but not for some others.

On my local i had tested the same with single database, it worked fine so we pushed the same to production.

I want to ensure if my approach was worng ( model changes + Manual DB changes) then why application worked fine for some of the database whithout any error.
Sachin Singh4y ago
Check you DB, there must be migration folder where the last migration file doesn't map to changes you are trying to push, meaning there is a gap in migrations, either you have deleted the migration file or added or updated something manually .
Better, delete the migration folder completely from server and then again run update-databse.
when you will run update-database it will create a migration file with whole DB schema that you won't re-run, though you can use -ignore switch but it doesn't work all the time so better remove everything from up() and down() method and execute update-database
--add-migration init

public partial class Initial : Migration
{
    protected override void Up(MigrationBuilder migrationBuilder)
    {
       // delete everything here
    }

    protected override void Down(MigrationBuilder migrationBuilder)
    {
       // delete everything here
    }
}

--update-database
Then again add another migration and check the Up() method , it should contain only the recent changes that are not pushed to DB yet.