Transaction Profiling report compares two Performance Summary reports
It is useful to think of the Transaction Profiling report as a comparison of two Performance Summary reports: one for the report data and one for the baseline data.
The report data is specified by the PROFILING(REPORT(...), FIELDS(...)...) operand. The baseline data is specified by the PROFILING(BASELINE(...), FIELDS(...)...) operand.
- Group and sort input records by key field values
- Summarize the values of non-key fields in each group of records (for example, as an average or a total)
The Transaction Profiling report consolidates the two sets of summarized data by finding a row of summarized baseline data whose key fields match a row of summarized report data. The Transaction Profiling report then compares the values of the non-key fields in the two matched rows. Rows of summarized baseline data whose key field values do not match any rows of summarized report data are discarded.
When designing a Transaction Profiling report, you might find it useful to first run the two Performance Summary reports. This enables you to review the two sets of summarized data separately, before using the Transaction Profiling report to consolidate and compare them. Note that the Report Form and the Baseline Form both affect how the Transaction Profiling report summarizes baseline data. The Transaction Profiling report summarizes baseline data according to the order of the fields in the Report Form, and using only those fields that occur in both the Baseline Form and the Report Form.