Tracing level

It is very much important, to track the cause of error. But, we have to take care of the performance also.

It is the level of details capture in the log file.  If we increase the amount of detail information it will reduce the performance. So we have to take care, while we choosing the tracing level.

Tracing Level	Description
Normal	Integration Service logs initialization and status information, errors encountered, and skipped rows due to transformation row errors, Summarizes session result, but not at the level of individual rows.
Terse	Integration Service logs initialization information, error messages, and notification of rejected data.
Verbose Initialization	Normal + the Integration Service logs additional initialization details, names of index and data files used, and detailed transformation statistics.
Verbose Data	Verbose Initialization + the Integration logs each row that passes into the mapping. Also where the Integration Service truncates string data fit the precision of a column and provides detailed transformation statistics. When we configure the tracing level to verbose data, the Integration Service writes row data for all rows in a block when it processes a transformation.