Built-in Sybase driver support plugin

For Sybase jobs, options such as Drop Constraints, Drop Indexes, and Disable Triggers can be configured either through the Masking Job GUI or via the Masking Job API. For details on API usage, see API Calls for managing masking job driver support tasks.

Tasks

Drop Constraints drops and re-creates only check and foreign key constraints. In order to drop and re-create primary key and unique constraints as well as the indexes associated with the constraints, enable Drop Indexes.

For in-place jobs:

1. Drop Constraints drops and re-creates check constraints on all columns and foreign key constraints on only masked columns.

2. Drop Indexes drops and re-creates indexes on only masked columns. This task also drops primary key constraints and unique constraints along with their associated automatically generated indexes.

3. Disable Triggers disables and re-enables triggers on only tables with masked columns.

For on-the-fly jobs, the tasks will execute on all columns/tables in the ruleset.

Task execution order

The order of the tasks is as follows:

Pre-job:

1. Drop Constraints

2. Drop Indexes

3. Disable Triggers

Post-job (mirrored order):

1. Enable Triggers

2. Create Indexes

3. Create Constraints

Enabling tasks on a job

For instructions on how to enable driver support tasks on jobs, see API calls for managing masking job driver support tasks.

Important considerations

1. If masking primary key fields:

   1. Use the same deterministic algorithms on primary key fields that reference each other, so that referential integrity is maintained when the masking transformation completes and all constraints are re-created.

   2. Enable both Drop Constraints and Drop Indexes.

2. If dropping indexes on masked fields with constraints is desired, enable both Drop Constraints and Drop Indexes. The implementation of the optimizations has been modified, such that Drop Constraints only drops constraints and keeps indexes automatically created and Drop Indexes handles dropping/recreating indexes.

Known limitations

1. Drop Constraints will only drop check and foreign key constraints. Drop Indexes will drop primary and unique constraints.

2. If masking a primary key field, if only Drop Constraints is enabled, the job will fail during the transformation. It is recommended to enable both Drop Constraints and Drop Indexes on any applicable job per the usage instructions above. In order to not have Drop Indexes enabled, adding a prescript that drops the desired constraints will also work, but note that this workaround may result in missing indexes.

3. If a column with a primary key or unique constraint is also a foreign key reference to another table, the column being referenced is not included in the ruleset.

4. A foreign key constraint on a masked column that references a table outside of the given ruleset will fail in pre-task Drop Constraints. Jobs can only be applied to a single schema, not multiple schemas.