Forum Discussion
Agregate table data on app server or inside power bi
- 5 months ago
Best practice is to prepare data in SQL (clean joins, standardize fields) but build a star schema in Power BI for reporting.
Avoid using one large denormalized ERP view directly in Power BI, as it hurts performance and model usability.
Instead, separate your model into fact tables (transactions) and dimension tables (lookups like asset, date, location).
Keep heavy transformations and data shaping in SQL, but define business logic and measures in DAX.
Only pre-aggregate in SQL when there is a proven performance need; otherwise, let the Power BI semantic model handle analytics.
Best practice is to prepare data in SQL (clean joins, standardize fields) but build a star schema in Power BI for reporting.
Avoid using one large denormalized ERP view directly in Power BI, as it hurts performance and model usability.
Instead, separate your model into fact tables (transactions) and dimension tables (lookups like asset, date, location).
Keep heavy transformations and data shaping in SQL, but define business logic and measures in DAX.
Only pre-aggregate in SQL when there is a proven performance need; otherwise, let the Power BI semantic model handle analytics.