In large numbers, transformation errors decrease the performance of the Data Integration Service. With each transformation error, the Data Integration Service pauses to determine the cause of the error and to remove the row causing the error from the data flow. The Data Integration Service typically writes the row into the mapping log file of the Data Integration Service logs.
Consider the following solutions for transformation error bottlenecks:
Check the mapping log file to see where the transformation errors occur and evaluate those transformation constraints.
Transformation errors occur when the Data Integration Service encounters conversion errors, conflicting mapping logic, and any condition set up as an error, such as null input. Check the mapping log file to see where the transformation errors occur. If the errors center around particular transformations, evaluate those transformation constraints.
Configure a lower tracing level.
If you need to run a mapping that generates a large number of transformation errors, it is possible to improve performance by setting a lower tracing level. However, this is not a recommended long-term solution to transformation errors.