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 previous comment the time out in the connection string is only used for opening the connection (standard SQL Client functionality). We provider a CommandTimeout property on migrations configuration to allow you to specify a time out for commands - http://msdn.microsoft.com/en-us/library/system.data.entity.migrations.dbmigrationsconfiguration.commandtimeout(v=vs.103).aspx .
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 previous comment the time out in the connection string is only used for opening the connection (standard SQL Client functionality). We provider a CommandTimeout property on migrations configuration to allow you to specify a time out for commands - http://msdn.microsoft.com/en-us/library/system.data.entity.migrations.dbmigrationsconfiguration.commandtimeout(v=vs.103).aspx .