If a script fails, or if it is cancelled, in most circumstances changes are rolled back. SQL Packager uses transactions to do this. However, there are some circumstances in which this is not possible:

• if full-text information must be altered
  For example, within a transaction, catalogs cannot be dropped, and indexing cannot be added to a column.
• if users and roles need to be created, altered, or deleted
  For example, within a transaction, a user cannot be created, or added to a role.

In these cases, SQL Packager rolls back all the changes that it can. Your database will be in an undetermined state.

If you have selected the schema packaging option Do not include plumbing for transactional synchronization scripts to remove transactions from the schema packaging script, or cleared the data packaging option Use transactions in SQL scripts to remove transactions from the data packaging script, no changes are rolled back when the script is cancelled or fails. This may be useful if you want to run a script up to the point of failure, for example for debugging.

SQL Packager always warns you if it is unable to roll back changes.