Skip to content

Built-in MSSQL Driver Support Plugin


The current implementation is simply the earlier implementation of the database masking options in the new driver support plugin framework. No optimizations have been implemented yet; stay tuned for optimizations in a future release.


For in-place jobs:

  1. Disable Constraints disables and re-enables constraints on all columns of the table(s) included in the job ruleset.
  2. Drop Indexes drops and re-creates indexes on only masked columns.
  3. Disable Triggers disables and re-enables triggers on all tables included in the job ruleset.

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

Task Execution Order


The order of task execution for built-in driver support plugins is fixed/unmodifiable.

The order of the MSSQL Driver Support tasks is as follows:


  1. Disable Constraints
  2. Drop Indexes
  3. Disable Triggers


  1. Disable Triggers
  2. Drop Indexes
  3. Disable 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.

Known Limitations

  1. Primary Key constraints are not disabled.
  2. Unique Constraints/Indexes are not disabled.
  3. Clustered Columnstore Indexes are not dropped.
  4. Functional Indexes are not dropped.
  5. As before, constraints are dropped on all columns of the table(s) included in the job ruleset.
  6. Referential integrity is not enforced, i.e., in the current implementation, there is no validation that a primary key or unique constraint column being referenced by a foreign key column are masked with the same deterministic algorithm.
  7. Disable Triggers is dropping the triggers on all tables in the ruleset irrespective of whether table is masked or not.