Register now to learn Fabric in free live sessions led by the best Microsoft experts. From Apr 16 to May 9, in English and Spanish.
I have a database I access which has lots of rows. I have it as a base level query for which I build lots of derivative (referenced) ones from it.
Reading online it doesn't seem like there's a way to have that base query be truly cached, and then the referenced ones can subslice as needed, to optimize for network access times.
Any good references on how to design for this?
Search these sites for table.buffer
Hi Matt,
Yes I've tried that already. Table.Buffer, seems to only really affect the downstream steps in a given query. It does NOT help for queries that reference base ones (cross-query).
TBH, I've tried this in the past, and even down stream steps intra-query don't seem to just use cached versions when edits are made, but always seem to refresh from data source whether a refresh is requested or a simple edit is made.
Covering the world! 9:00-10:30 AM Sydney, 4:00-5:30 PM CET (Paris/Berlin), 7:00-8:30 PM Mexico City
Check out the April 2024 Power BI update to learn about new features.
User | Count |
---|---|
105 | |
97 | |
80 | |
67 | |
63 |
User | Count |
---|---|
147 | |
110 | |
108 | |
85 | |
64 |