When executing a migration from the console on a database with a table containing 30-50 columns and 1million rows the migration fails with a timeout exception regardless of the timeout parameter in the connection string and the timeout set on the server. It appears to time out after approx 1 minute.
It would be very useful to have an explicit timeout switch or at the very least for it to use the one in the connection string.
Note: when running the migration from within Visual Studio this does not occur.
Comments: Per Brice's comment, it seems that this is already fixed with the DbMigrationsConfiguration.CommandTimeout property. Marking for re-triage to confirm.
It would be very useful to have an explicit timeout switch or at the very least for it to use the one in the connection string.
Note: when running the migration from within Visual Studio this does not occur.
Comments: Per Brice's comment, it seems that this is already fixed with the DbMigrationsConfiguration.CommandTimeout property. Marking for re-triage to confirm.