Don't miss your chance to take the Fabric Data Engineer (DP-600) exam for FREE! Find out how by attending the DP-600 session on April 23rd (pacific time), live or on-demand.
Learn moreNext up in the FabCon + SQLCon recap series: The roadmap for Microsoft SQL and Maximizing Developer experiences in Fabric. All sessions are available on-demand after the live show. Register now
Hi.
I've got a large dataset (2 weeks, 2mln rows, 52 weeks - >100m rows), of End User communication, that looks something like this.
Communication status column = "Success", represents 2 emails delivered to the recipient.
Communication status column = "READ_ACK" represents an open email.
For calculation of the same email open rate per visitor I use a variable approach, where:
var v = visitorid
var t = template (because I need to see if the same email was open)
However, per such large data set, It is very tedious and slow to perfom complex variable calculations (this is only one of them). The report slows down drastically due to all calculated columns.
Is there anyone that has faced the similar issue and knows any solutions to this?
Thanks,
Ed
Solved! Go to Solution.
DAX works much better with skinner and longer table rather than wider and shorter ones. Looks like you have alot columns in that one table. Possible to denormalize some of that? ( ie. really dont need day of week and week number in your fact table if you have a date table).
@Anonymous ,
Yes, as nick mentioned, you could remove some columns to improve the performance. About how to improve your report and optimize your model, I would suggest you to refer to doc below:
https://docs.microsoft.com/en-us/power-bi/power-bi-reports-performance
Community Support Team _ Jimmy Tao
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
@Anonymous ,
Yes, as nick mentioned, you could remove some columns to improve the performance. About how to improve your report and optimize your model, I would suggest you to refer to doc below:
https://docs.microsoft.com/en-us/power-bi/power-bi-reports-performance
Community Support Team _ Jimmy Tao
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
DAX works much better with skinner and longer table rather than wider and shorter ones. Looks like you have alot columns in that one table. Possible to denormalize some of that? ( ie. really dont need day of week and week number in your fact table if you have a date table).
If you have recently started exploring Fabric, we'd love to hear how it's going. Your feedback can help with product improvements.
A new Power BI DataViz World Championship is coming this June! Don't miss out on submitting your entry.
Share feedback directly with Fabric product managers, participate in targeted research studies and influence the Fabric roadmap.
| User | Count |
|---|---|
| 48 | |
| 45 | |
| 41 | |
| 20 | |
| 17 |
| User | Count |
|---|---|
| 69 | |
| 64 | |
| 32 | |
| 31 | |
| 27 |