When you configure a SQL transformation with stored procedure and use in, out, and in-out parameters for columns of SUPER data type, the mapping fails with the following warning:

When you enable the staging optimization property for lookups configured to use persistent cache, the mapping fails at runtime for consecutive runs. (July 2023)

When you read from an Amazon Redshift source table that has NULL data in char data type and then configure the staging optimization property, the mapping is successful but there is a mismatch in the data that is written to the target. (April 2023)

When you enable the staging optimization property with the unload command ESCAPE=OFF and run a mapping to read from an Amazon Redshift source that have data delimiters, the data written to the target is truncated until the delimiter value. (April 2023)

When you enable the staging optimization property for the source and run a parameterized mapping, the mapping task runs without optimizing the performance. (April 2023)