Configure schema drift alerts - Precisely Data Integrity Suite

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

Configure schema drift alerts to detect changes in table and column metadata. Schema drift rules generate alerts when tables or columns are added, deleted, renamed, or when column data types change.

Schema is the source of your data. Any changes in the metadata of the source can cause severe downstream data issues. Configure schema drift alerts to receive notifications when tables or columns are added, deleted, renamed, or when column data types change. You can set different alert levels (critical, warning, or none) for each type of schema change based on its impact to your data. Schema drift alerts trigger instantly after a consecutive run whenever the schema changes, regardless of the alert type you configure. For more information, see Configure rule based alerts.

To configure schema drift alerts:
  1. Go to Observability > Observers and select + Create Observer.
  2. On the Create Observer page, select your data assets and click Next.
  3. In the Schema Drift row, click the gear icon in the Configure column.
  4. For each schema change scenario, select an alert type.

    Schema change scenarios:

    • Table is deleted
    • Table is renamed
    • Column is deleted
    • Column is renamed
    • New column added
    • Column data type changed

    Alert types:

    • Critical: Generates a critical alert for high-impact schema changes.
    • Warning: Generates a warning alert for moderate-impact schema changes.
    • None: No alert is raised for this schema change.
    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 deleted or renamed, set those scenarios to Critical Alert. For less critical changes like adding optional columns, you can select Warning Alert or None.
  5. Click Save.

For more information about schema metadata, see SVV_TABLE_INFO (Redshift) or pg_xact_commit_timestamp (PostgreSQL).