can be configured to automatically detect some source schema changes and handle these changes on the target. This process is referred to as
schema drift
.
Mass Ingestion Databases
can detect the following types of source schema changes:
Add column
Modify column
Drop column
Rename column
This feature is available for database ingestion incremental load tasks and combined initial and incremental load tasks that propagate change data from Microsoft SQL Server or Oracle sources to Amazon Redshift, Google BigQuery, Kafka, Microsoft Azure Synapse Analytics, Oracle, or Snowflake targets, or from a PostgreSQL source to Amazon Redshift, Google BigQuery, Kafka, Microsoft Azure Synapse Analytics, or Snowflake targets. By default, this feature is
not
enabled.
When you define a task, on the
Schedule and Runtime Options
page of the database ingestion task wizard, you can configure the types of source schema changes to propagate and how to handle them. For example, you can configure schema drift options to ignore the changes, replicate them, or stop the job or subtask when a schema change occurs. For more information, see
Configuring schedule and runtime options.
If you try to replicate a type of schema change that is not supported on the target, the database ingestion job ends with an error.
Mass Ingestion Databases
does not replicate source changes that add, remove, or modify primary key or unique key constraints. If these types of changes occur on the source, you must resynchronize the target tables.
If you configured schema drift options to stop the job when
Mass Ingestion Databases
detects a schema change, you can use the
Resume With Options
command to resume the job with an override schema drift option.
Mass Ingestion Databases
detects a schema change in a source table only after DML operations occur on the altered source table. If multiple schema changes occur without intervening DML operations,
Mass Ingestion Databases
detects all of the schema changes at one time, when a DML operation occurs. To ensure that
Mass Ingestion Databases
detects all of the supported schema changes correctly, Informatica recommends that you apply schema changes to source tables one by one, each followed by at least one DML change.
Database ingestion tasks that have Microsoft Azure Synapse Analytics targets cannot replicate rename operations on source columns. The Replicate option is not available.
Database ingestion tasks that have Snowflake targets support modify operations on source columns with the following limitations:
Snowflake targets cannot modify the scale of NUMBER columns.
Snowflake targets do not support changing the data type of an existing column to a different data type.
Database ingestion tasks that have Google BigQuery targets cannot replicate rename or modify operations on source columns. The schema drift options for these operations are not available.
ASK INFAPreview
