Share feedback directly with Fabric product managers, participate in targeted research studies and influence the Fabric roadmap.
Sign up nowGet Fabric certified for FREE! Don't miss your chance! Learn more
what could be the reasons for not implementing KPIs business logic in database and implementing their business logic only in Power BI , one such example is we cannot implement aggregated measures such as Sum(), Avg() inside database because Aggregated measures can be sliced and diced across any dimensions in report however in database aggregation must be applied across certain specific dimension
Solved! Go to Solution.
Why KPIs are often built in Power BI, not in the database:
- Dynamic slicing: Power BI measures adapt to any filter or dimension; SQL needs fixed GROUP BY.
- Interactivity: KPIs respond to slicers, drill-throughs, bookmarks—SQL can’t.
- Performance: Power BI caches data; SQL recalculates every time.
- Time intelligence: DAX handles YTD, rolling averages, fiscal calendars better than SQL.
- Governance: Easier versioning and control in Power BI than altering DB logic.
Hi @powerbiexpert22 ,
Since we didnt hear back, we would be closing this thread.
If you need any assistance, feel free to reach out by creating a new post.
Thank you for using Microsoft Community Forum
Hi @powerbiexpert22 ,
Just wanted to check if you got a chance to review the suggestions provided and whether that helped you resolve your query?
Thank You
Hi @powerbiexpert22 ,
I hope the information provided above assists you in resolving the issue. If you have any additional questions or concerns, please do not hesitate to contact us. We are here to support you and will be happy to help with any further assistance you may need.
Thank You
In relational databases like SLQ server, measures do not exist and cannot be reused
If this helped, please consider giving kudos and mark as a solution
@me in replies or I'll lose your thread
Want to check your DAX skills? Answer my biweekly DAX challenges on the kubisco Linkedin page
Consider voting this Power BI idea
Francesco Bergamaschi
MBA, M.Eng, M.Econ, Professor of BI
Why KPIs are often built in Power BI, not in the database:
- Dynamic slicing: Power BI measures adapt to any filter or dimension; SQL needs fixed GROUP BY.
- Interactivity: KPIs respond to slicers, drill-throughs, bookmarks—SQL can’t.
- Performance: Power BI caches data; SQL recalculates every time.
- Time intelligence: DAX handles YTD, rolling averages, fiscal calendars better than SQL.
- Governance: Easier versioning and control in Power BI than altering DB logic.
If you love stickers, then you will definitely want to check out our Community Sticker Challenge!
Check out the January 2026 Power BI update to learn about new features.
| User | Count |
|---|---|
| 65 | |
| 64 | |
| 45 | |
| 21 | |
| 18 |
| User | Count |
|---|---|
| 115 | |
| 114 | |
| 38 | |
| 36 | |
| 26 |