March 31 - April 2, 2025, in Las Vegas, Nevada. Use code MSCUST for a $150 discount! Early bird discount ends December 31.
Register NowBe one of the first to start using Fabric Databases. View on-demand sessions with database experts and the Microsoft product team to learn just how easy it is to get started. Watch now
Hello PBI Community! 🙂
I have a query (QueryA) where I need to extract two columns (date and description), and I create a calendar based on this two columns.
I am doing this using "=QueryA", and then I remove the columns/rows I don't need.
This is working fine, but I want to do one extra step to improve the refresh performance.
"QueryA" is really big, and receives around 150k new rows each month.
In the description column, I have two categories that I use ONLY to create the calendar, and I want to remove all rows that have this information after I create "QueryB".
The point is, after I create "QueryB" (=QueryA), if I remove the rows I don't need from "QueryA", they won't appear on "QueryB", as ="QueryA" references the last step I created on "QueryA".
Is there any workaround?
Removing this rows would remove around 50k rows/month, so in the long term this would make a huge difference...
Thanks in advance! 🙂
Solved! Go to Solution.
Have you tried creating a non-loaded common BaseQuery, which is referenced by QueryA (which removes the data that's only needed by QueryB) and QueryB (which creates the calendar table)?
Have you tried creating a non-loaded common BaseQuery, which is referenced by QueryA (which removes the data that's only needed by QueryB) and QueryB (which creates the calendar table)?
Helo Ehren!
I actually didn't think of it... 🤐
Thanks for your help!!
March 31 - April 2, 2025, in Las Vegas, Nevada. Use code MSCUST for a $150 discount!
Arun Ulag shares exciting details about the Microsoft Fabric Conference 2025, which will be held in Las Vegas, NV.