Starting December 3, join live sessions with database experts and the Microsoft product team to learn just how easy it is to get started
Learn moreGet certified in Microsoft Fabric—for free! For a limited time, get a free DP-600 exam voucher to use by the end of 2024. Register now
Hi Everyone,
I have two tables which are called Email and Blocks. Email has unique segment based deliveries and Blocks has more rows for each block email has. My issue is that I'm having trouble with a matrix visual which is not possible to display the visual because of the memory (even with 10 GB space in premium server). Dataset size is around 50 MB.
Email Table Structure:
245k rows and more columns than below
Blocks Table Structure:
800k rows and more columns than below
I use CommonKey to create relationship and I also have a Region and calendar table to map dates and regions. What I want to achieve is EmailTitle, Date, Country and Block Name based metrics as below:
But it gives me out of memory error and I think
Solved! Go to Solution.
If you have a dimension table for EmailTitle and a date table for Date and you use the columns from these dimension tables in your visual, then I wouldn't expect memory issues.
In general, it's not a good idea to create relationships between fact tables like you've done here. I'd recommend removing that relationship and constructing your visual with dimension table columns instead.
Hi @Anonymous ,
1. Please kindly check how much RAM and CPU Power BI is taking. And refer the official document to optimize the data model.
Hope these help:
https://community.powerbi.com/t5/Power-Query/How-to-Optimize-Memory-Usage/td-p/57915
2. You can download and install Dax Studi for query, display the content on the "All queries" page, find the query with the longest running time and analyze it:
3. You can also try head to "Data Cache Management Options", clear cache or increase the "maximum allowed" figure.
This is the related document, you can view this content:
Best Regards,
Liu Yang
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
If you have a dimension table for EmailTitle and a date table for Date and you use the columns from these dimension tables in your visual, then I wouldn't expect memory issues.
In general, it's not a good idea to create relationships between fact tables like you've done here. I'd recommend removing that relationship and constructing your visual with dimension table columns instead.
Starting December 3, join live sessions with database experts and the Fabric product team to learn just how easy it is to get started.
March 31 - April 2, 2025, in Las Vegas, Nevada. Use code MSCUST for a $150 discount! Early Bird pricing ends December 9th.
User | Count |
---|---|
94 | |
83 | |
82 | |
71 | |
49 |
User | Count |
---|---|
143 | |
129 | |
108 | |
63 | |
55 |