Don't miss your chance to take the Fabric Data Engineer (DP-700) exam on us!
Learn moreThe FabCon + SQLCon recap series starts April 14th at 8am Pacific. If you’re tracking where AI is going inside Fabric, this first session is a can't miss. Register now
Hi,
I noticed that we have 25 date tables (called "LocalDateTable") which I believe are related to time intelligence. In DAX Studio's VertiPaq Analyzer, I observed large sizes between these date columns and other columns in different tables within the Relationships section. This significantly affects memory usage during refresh.
These Date tables are only visible in Analysis Services and not in the Power BI data model.
Is there anything I can do to ignore these tables during the refresh process? I think they are eating memory, and I haven't been able to address the issue yet.
Thanks!
@hoosha_11 Turn off auto-time intelligence. File | Options and settings | Options | CURRENT FILE | Data Load | Time Intelligence | Auto date/time. Turn that off.
I turned it off, published and refreshed, but the visuals in the reports won't load.
@hoosha_11 Well, if you used auto-time intelligence in something then that could cause a problem. Auto TI syntax is like [Date].[Month]. It's the .[Month] part that is how the underlying tables are referenced. So, you need to get rid of those and just use MONTH([Date]) for example.
Also, if you used the Date Hierarchy in a visual versus just the Date then that would also cause problems.
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 |
|---|---|
| 29 | |
| 23 | |
| 17 | |
| 16 | |
| 14 |