Skip to main content

Defining Global transformations

Use Global transformations to make similar changes to multiple tables, owners, and columns in the same task.


Global transformations are not available in a Log Stream Staging setup.

For information on Log Stream Staging, see Using the Log Stream.

You may need to use this option when you want to change the names of all tables. You can change the names using wildcards and patterns. For example, you may want to change the names of the tables from account_% to ac_%. This is helpful when replicating data from an Microsoft SQL Server endpoint to an Oracle endpoint where the Microsoft SQL Server endpoint has a limit of 128 characters for a table name and the Oracle endpoint has a limit of 31 characters.

You may also need to change a specific data type in the source to a different data type in the target for many or all of the tables in the task. Global transformation will accomplish this without having to define a transformation for each table individually.


Table-specific transformations override global transformations. For example, you can define a global transformation that changes the data type for all tables from DATE to DATETIME(6) and then define another transformation for a specific table that changes the data type from DATE to STRING(50).

For information on defining a transformation for a specific table, see Defining Transformations for a Single Table/View.

This section includes the following topics: