SQL Packager - 6.4

SQL Packager

Setting data packaging options - SQL Packager

The data packaging options are a set of advanced features that enable you to modify the behavior of SQL Packager when it packages data. For example, you can set options so that triggers are disabled when you upgrade a database and then, when the upgrade is complete, re-enable the triggers.

You can also set:

Disable foreign keys

Disables foreign keys before creating or upgrading the database, and re-enables them on completion. Note that in some circumstances foreign keys will be dropped and recreated rather than disabled and re-enabled.

Disable DML triggers

Disables DML triggers before creating or upgrading the database, and re-enables them on completion.

For example, you may want to disable triggers if you have a trigger defined on a table that inserts data into another table on INSERT, DELETE, or UPDATE; if you do not, the data in the tables will change as the package is run, which will cause unpredictable results.

Drop primary keys, indexes and unique constraints

Drops then recreates primary keys, indexes (including XML indexes and partitioned indexes), and unique constraints before creating or upgrading the database, and re-enables them on completion. If the primary key, index, or unique constraint is the comparison key, it cannot be dropped.

Select this option to ensure that unique constraints are not violated when data is inserted into tables or modified. When the constraints are re- created, the data is verified to ensure that no constraints have been violated. (If they have, the script will fail.)

Do not use transactions in synchronization SQL scripts

Removes transactions from the synchronization SQL scripts to produce SQL code that is more readable.

If this option is not selected and the synchronization script fails, the script is rolled back to the start of the failed transaction. If this option is selected, the script is not rolled back. This can be useful for detection of errors within a script.

Transport CLR types as binary

This option is used only for SQL Server 2008 and SQL Server 2005 databases.

If this option is selected, SQL Packager uses the binary representation of CLR types; if this option is not selected, SQL Packager uses the string representation. Note that string representations do not always contain the full information about the data.

Disable DDL triggers

This option is used only for SQL Server 2008 and SQL Server 2005 databases.

Disables DDL triggers before creating or upgrading the database, and re-enables them on completion.

Reseed identity columns

Reseeds identity values in the database you are updating after synchronization.

Trim trailing spaces

If the data in two columns differs only by the number of spaces at the end of the string, SQL Packager considers the data to be identical. This option does not apply to CLR or XML columns.

If this option is selected, trailing spaces are ignored when creating or upgrading databases.

Force binary collation

SQL Packager uses keys to compare rows. If the comparison key is a string, this option forces a binary collation on all string sorting.

Use checksum comparison

Performs a checksum prior to comparison. The data is compared only if the checksums differ. Note that if the data differs only in text or image columns, the checksums will be identical and SQL Packager will consider the data to be identical.

For SQL Server 2000, db_owner permissions are required.

Ignore case

When you are upgrading a database, SQL Packager will ignore the case of the object names, if this option is selected. For example, SQL Packager will consider [dbo].[Widget] to be the same as [dbo].[wIDgEt] and will compare the data in the two tables.

Note that if the databases that you are upgrading are running on a SQL Server that uses case-sensitive sort order, you should ensure that this option is cleared.

Ignore spaces

When you are upgrading a database, SQL Packager will ignore spaces in object names, if this option is selected. For example, SQL Packager will consider [dbo].[Widget Prices] to be the same as [dbo].[WidgetPrices] and will compare the data in the two tables.

Ignore underscores

When you are upgrading a database, SQL Packager will ignore underscores in object names, if this option is selected. For example, SQL Packager will consider [dbo].[Widget_Prices] to be the same as [dbo].[WidgetPrices] and will compare the data in the two tables.

Include views

If this option is selected, SQL Packager includes views in the upgrade. Generally, views can be updated only if the referenced rows are from a single table, and the referenced columns are simple (for example, they must not include identity columns or computed columns).

Include timestamp columns

If this option is selected, SQL Packager will compare timestamp columns when you are upgrading a database. Note that timestamp columns cannot be included in the data packaging script.

Include identity columns

Includes identity columns in the package. Note that if you do not select this option and an identity column is used as the primary key for a table, it will be included in the packaging script.

See also

Setting packaging options

Setting schema packaging options

Setting SQL Packager options

Was this article helpful?

Search support
Forums
Visit the SQL Packager forum.
Learning SQL Packager
Knowledge base

SQL Packager

all SQL products

all products

Notes & articles

SQL Packager

all SQL products

all products

Demos & walkthroughs

SQL Packager