Reporting on multiple tables
Hi Team,
We are looking for an optimized performance solution to report on multiple tables and putting filteration logic over them to extract data.
Which solution is best in terms of performance:
- Pulling data from Report definition direction via joins over the classes and filteration in place
- Creating a view which joins all the tables and report definition work on that view
Is there any real benefit of RD with view over RD with joins?
** We cannot use MATERIALIZED VIEW as the data changes will be frequent in nature.
Maantic Technologies Pvt Ltd.
IN
Hi @ShwetaB96,
Only additional advantage I see on creating a view which joins all the tables and report definition work on that view, is that the join happens in the DB side which is comparatively much faster. However the disadvantage is that the logic is encapsulated in the DB query which cannot be changed from Pega and hence maintenance wise not good.
You may decide which is more important to you performance or maintenance? If the logic that you are encapsulating in the view query is complex and you prefer to do it using a view go for the solution where you create a view which joins all the tables and report definition work on that view. If the logic is not too complex then I would recommend you to keep the logic in Pega by using a join in the Pega report definition.