Report definition generates dynamic column alias
When running a report, DB2 Generated SQL has a dynamic column alias which causes performance hit. Environment remains responsive, but database responsiveness is excessively slow to respond to Pega engine.
Steps to Reproduce
Create a report definition against DB2 table with one of the column name 'large', for example 'CURRENT_STEP_SECONDARY_HOLDER_NM'
and run the report and check the generated sql in the tracer
A defect or configuration issue in the operating environment:
Pega generates a dynamic column alias for any column name that exceeds 30 characters. The 30 character limit represents the smallest maximum column name length of any of the databases we support (in this case Oracle).
An enhancement request, FDBK-17044, has been created for consideration by Pega Product Management.
0% found this useful