Posted: 18 May 2015 13:11 EDT Last activity: 27 Aug 2015 16:32 EDT
Exposing more than 150 columns
Hi - We have a reporting requirement where in atleast some 150 columns required to be exposed. By doing this PEGA will have to put a copy in the individual column as well as in BLOB which may slow down the overall performance. Is there any better option?
true, too many exposed columns can cause DB paging/memory issues leading to poor performances. all that said, exposed columns are mostly referenced for reporting purposes. so would decomposing the table or BIX or Index tables can be of use alternatives here??
The way to do this is to use a declarative index. The index table will not have a blob; as long as your SQL statements (PRPC report definitions, activities, etc) are optimized, performance with >150 exposed columns (in the index table) is not affected.
According to the Pega 7.1.8 platform support guide (available on the PDN) several versions of IBM DB2 are supported for LUW (Linux, Unix, and Windows) as well as z/OS operating systems. I would download this document and review it for your specific platform combination. If you still have a question, you should contact Pega Global Customer Support (GCS) with your specific needs.