Commented Issue: Migrate from console does not follow timeout param in connection string [893]

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: The timeout in the connection string only refers to the timeout of connecting to the database. To specify the timeout of executing the commands, use DbMigrationsConfiguration.CommandTimeout.