Rollback changes when SQL Packager generated installer fails

golgotha1

Is there a way to force the database upgrade installer generated from SQL Packager to rollback any changes made by the installer to the target database prior to an error being generated?

Michelle T

If you're using a SQL Packager-generated script (as opposed to packaging your own script), and haven't unselected the option to use transactions, it ought to roll back all the changes that can be rolled back. Changes that may still cause problems include user/login/security objects and full text cataloguing objects (because these objects can't always be created / altered within a transaction).