When you want to include quite a lot of SQL in a migration it is nice to be able to put it in a separate SQL file rather than inline in the code. It would be good if Migrations had a means to easily reference the SQL file rather than having to load it manually.
Comments: The other thing this should do is split on "GO" in the script into separate queries, at least for SQL Server, since you can't actually send "GO" using ExecuteNonQuery.
Comments: The other thing this should do is split on "GO" in the script into separate queries, at least for SQL Server, since you can't actually send "GO" using ExecuteNonQuery.