6

Very simple question, i am using migrations in entity framework 6, and like the command

update-database -script

But is there a way of generating the script but have it wrapped with a transaction?

Problem is that if the script fails, i have to unpick it

Gillardo
  • 9,518
  • 18
  • 73
  • 141
  • You could take this approach, although tedious: http://stackoverflow.com/questions/18528376/code-first-migrations-update-database-script-command-generated-sql-script-not – Steve Greene Aug 14 '15 at 16:06

1 Answers1

11

This is what I'm using only on release mode to generate the scripts:

public class MigrationScriptBuilder : SqlServerMigrationSqlGenerator
{
#if !DEBUG
    protected override void Generate(SqlOperation sqlOperation)
    {
        Statement("GO");

        base.Generate(sqlOperation);

        Statement("GO");
    }

    public override IEnumerable<MigrationStatement> Generate(IEnumerable<MigrationOperation> migrationOperations, string providerManifestToken)
    {
        yield return new MigrationStatement {Sql = "BEGIN TRAN"};

        foreach (var migrationStatement in base.Generate(migrationOperations, providerManifestToken))
        {
            yield return migrationStatement;
        }

        yield return new MigrationStatement {Sql = "COMMIT TRAN"};
    }
#endif
}

You should wire that in your DatabaseMigrationsConfiguration. Example:

public sealed class DatabaseMigrationsConfiguration : DbMigrationsConfiguration<DatabaseContext>
{
    public DatabaseMigrationsConfiguration()
    {
        SetSqlGenerator("System.Data.SqlClient", new MigrationScriptBuilder());
    }
}
regisbsb
  • 3,664
  • 2
  • 35
  • 41