Share feedback directly with Fabric product managers, participate in targeted research studies and influence the Fabric roadmap.
Sign up nowGet Fabric certified for FREE! Don't miss your chance! Learn more
Hi!
Can you share with me situations where the functions Table.Buffer is recommended? Or some scenarios, you used this function successfully.
Hi, if you need to use the same table multiple times in your data transformation process, buffering it can save processing time (better performance) by loading the data into memory once and then referencing it multiple times.
For example when joining large tables, buffering the larger table can be beneficial to avoid unnecessary data refreshes during the join operation:
In this example, before using the main table for merging, we have first buffered it to expedite the merge process. By buffering the table, the merge operation becomes faster due to reduced data retrieval and improved in-memory processing efficiency.
Of course it has other applications as well.
Share feedback directly with Fabric product managers, participate in targeted research studies and influence the Fabric roadmap.
| User | Count |
|---|---|
| 7 | |
| 4 | |
| 4 | |
| 3 | |
| 3 |
| User | Count |
|---|---|
| 12 | |
| 11 | |
| 11 | |
| 7 | |
| 6 |