Closed
Description
I don't know if this is just not an intended use for migration files, but I'm trying to seed postal code data in a migration. To me it makes sense because it is a default set of data that my my application will need in order to run and the table is meaningless without its data. Since it is tens of thousands of rows to insert, it takes a while to complete and Evolve's command is timing out. We tried breaking it up into smaller batches using "GO" (this is SQL Server 2016), but it still times out. Maybe we just didn't go small enough on the batches (they only take about 12 seconds to execute individually in SSMS) but is there a way to configure the command timeout?