Forum Discussion
Performance Issues in Customer-Centric Power BI Model (Large Dataset)
Hi all,
I’m building a customer-centric PBI dashboard using a large dataset for the 12 months (43,617,492 rows) already aggregated at customer-month level (not transactional).
It includes multiple dimensions (country, region, product, months etc.).
The report has time trends, composition charts, and many slicers.
I need dynamic KPIs like active, new, lost customers, churn, retention, and YoY %, depending on user-selected periods (1+ months), plus averages per customer. Example of measure for Active Customers:
Active_Customers =
VAR Customers =
SUMMARIZE(
DB_CUSTOMER,
DB_CUSTOMER[Customer_id]
)
RETURN
COUNTROWS(
FILTER(
Customers,CALCULATE([Current Year Shipments]) > 0))
I’m facing: Slow performance, Query execution conflict errors,High Capacity Unit (CU) consumption spikes
Constraints:
- Must keep full customer base
- Metrics rely on customer-level calculations over time
What I’m Looking For
I’d appreciate guidance on:
- Best practices to optimize this kind of customer-based KPI model at scale
- Whether my issue is more likely due to:
- Data model design
- DAX complexity (especially YoY + status calculations)
- Capacity / Fabric configuration
- Suggested approaches such as:
- Further aggregation strategies
- Hybrid tables / incremental refresh
- Calculation optimization
- Alternative modeling patterns for customer lifecycle metrics
Thanks in advance for your help! Happy to provide more technical details if needed.
Hi 3508026 ,
Thank you for contacting the Microsoft Fabric Community. When handling customer level KPIs with a large dataset, you may experience performance issues due to the data model or DAX logic. Microsoft recommends using a star schema, simplifying your measures, and applying aggregation tables or incremental refresh to help reduce workload. CU spikes and query conflicts are common in shared capacity, so for more consistent performance, Premium or Fabric capacity provides dedicated resources.
For more information, please refer to the attached document.
Configure incremental refresh and real-time data for Power BI semantic models - Power BI | Microsoft Learn
Understand star schema and the importance for Power BI - Power BI | Microsoft Learn
What is Power BI Premium? - Microsoft Fabric | Microsoft LearnI hope this clarifies the situation. If I’ve misunderstood any part of your situation, please let us know.
3 Replies
- V-yubandi-msftCommunity Support
Hi 3508026 ,
Thank you for contacting the Microsoft Fabric Community. When handling customer level KPIs with a large dataset, you may experience performance issues due to the data model or DAX logic. Microsoft recommends using a star schema, simplifying your measures, and applying aggregation tables or incremental refresh to help reduce workload. CU spikes and query conflicts are common in shared capacity, so for more consistent performance, Premium or Fabric capacity provides dedicated resources.
For more information, please refer to the attached document.
Configure incremental refresh and real-time data for Power BI semantic models - Power BI | Microsoft Learn
Understand star schema and the importance for Power BI - Power BI | Microsoft Learn
What is Power BI Premium? - Microsoft Fabric | Microsoft LearnI hope this clarifies the situation. If I’ve misunderstood any part of your situation, please let us know.
- V-yubandi-msftCommunity Support
Hi 3508026 ,
If you get a chance, please review the response and let us know if it aligns with your expectations. Should you need any additional details or clarification, feel free to let us know.
Regards,
Yugandhar.
- V-yubandi-msftCommunity Support
Hi 3508026 ,
Could you please let us know if your issue has been resolved, or if you still need any additional details or clarifications from our side.
Thank you.