Schema drift rule

Data Integrity Suite

Product
Spatial_Analytics
Data_Integration
Data_Enrichment
Data_Governance
Precisely_Data_Integrity_Suite
geo_addressing_1
Data_Observability
Data_Quality
dis_core_foundation
Services
Spatial Analytics
Data Integration
Data Enrichment
Data Governance
Geo Addressing
Data Observability
Data Quality
Core Foundation
ft:title
Data Integrity Suite
ft:locale
en-US
PublicationType
pt_product_guide
copyrightfirst
2000
copyrightlast
2026

Schema is the source of your data. Any changes in the metadata of the source can cause severe downstream data issues. You can configure the schema drift rule to receive alerts for changes in a table or column. These changes can include the addition, deletion, or renaming of a table or column, or changes to a column data type.The type of alert is determined by how you configure the rule.For example, you can set the deletion of a column as a critical alert and renaming of a column as a warning alert.

Use these steps to create a schema drift rule during Observer creation.

  1. After you select the data assets to observe on the Create Observer page, click Next.
  2. In the Schema Data Drift row, click the gear icon in the Configure column.You can set the alerts to be generated in the following scenarios:
    Alerts can be raised if a:
    • Table is deleted
    • Column is deleted
    • New column added
    • Column datatype changed
  3. For each schema change, select an alert type.
    • Critical: Generates a critical alert.
    • Warning: Generates a Warning alert.
    • None: No alert is raised.
    Tip: Select an alert type that reflects the criticality of the data, For example, if a specific table is very critical and can cause issues if renamed, then set Table is renamed to a Critical Alert. For less critical changes, you can select a Warning Alert.
  4. Click Save.