Each database table in a rule set supports three optional attributes that control how data is selected and processed during compliance jobs: Custom SQL, Filter, and Logical Key. You can set these attributes during rule set creation or update them later.

Database column nullability

During rule set synchronization, DCT records whether each database column accepts null values in the is_nullable field. For Compliance Engines running version 2025.5.0 or later, DCT updates this value during each synchronization. A manually set value is overwritten during the next synchronization.

When is_nullable is false, DCT rejects an algorithm assignment if the algorithm can return null values. This validation also applies when changing the data class causes DCT to assign a default algorithm. If the column nullability is unknown, is_nullable is null and DCT treats the column as nullable.

This validation applies when a database column metadata record is updated. It does not apply to bulk imports, profiling, rule set refreshes, or job execution.
Attribute Description
Custom SQL A custom SQL query that replaces the default table scan when the compliance job reads data from this table. Use this to limit the columns or rows retrieved, or to join data from other tables before processing.
Filter A WHERE clause applied to the table during the compliance job. Only rows matching the filter condition are included in discovery or masking operations. Equivalent to appending a WHERE clause to the default SELECT statement.
Logical Key One or more columns used to uniquely identify rows in the table when no primary key is defined in the database. The compliance engine uses the logical key to match source and target rows during in-place masking operations.

Edit attributes on a single table

Use this task to set or update Custom SQL, Filter, or Logical Key for an individual table in a rule set.

  1. In the left navigation pane, click Compliance > Rule Sets.

  2. Click View next to the rule set you want to modify.

  3. Open the Masking Rules tab.

  4. Locate the table you want to update.

  5. Click Actions next to the table row and select the attribute you want to set: Edit Custom SQL, Edit Filter, or Edit Logical Key.

  6. Enter the value in the dialog and click Save.

Edit attributes for all tables in bulk

Use the bulk edit actions to apply a Filter or Logical Key to all tables in the rule set at once. Bulk edit is available for Filter and Logical Key only; Custom SQL must be set per table.

  1. In the left navigation pane, click Compliance > Rule Sets.

  2. Click View next to the rule set you want to modify.

  3. Open the Masking Rules tab.

  4. At the top of the page, click Edit Filter for All Tables or Edit Logical Key for All Tables.

  5. Enter the value to apply across all tables and click Save.

Set attributes during rule set creation

Table attributes can also be configured at the time a rule set is created. In the Data Tables step of the rule set creation wizard, each table row includes actions to set Custom SQL, Filter, and Logical Key before the rule set is submitted. For step-by-step instructions, see Create a rule set.

Set table attributes with CSV

DCT exported CSV supports table-level filter values, including Custom SQL, Where Clause, Having Clause, and Key Column and preserves these values during import.

Continuous Compliance exports do not include table filter conditions. After importing a Continuous Compliance file, review each affected table and restore any required conditions.

Last updated
Oct 8, 2026