Join us at FabCon Atlanta from March 16 - 20, 2026, for the ultimate Fabric, Power BI, AI and SQL community-led event. Save $200 with code FABCOMM.
Register now!To celebrate FabCon Vienna, we are offering 50% off select exams. Ends October 3rd. Request your discount now.
I'm currently working on implementing a merging strategy within a Fabric Data Warehouse environment, where I need to merge data from a stage table to a target table.
In my Azure SQL workflows, I typically use temporary tables for batch processing. However, my understanding is that temporary tables are not supported in Fabric Data Warehouse.
I could use CTEs, but their ephemeral nature poses some challenges. I could also persist tables and drop them once they are no longer needed. What else?
Solved! Go to Solution.
Hi @smoqt there are not that many options in the Fabric Warehouse service itself in terms of holding data for processing while using SQL. I would use persisted tables and drop them after they are no longer used.
Hi @smoqt there are not that many options in the Fabric Warehouse service itself in terms of holding data for processing while using SQL. I would use persisted tables and drop them after they are no longer used.
Thanks for the info. I wanted to make sure I wasn't missing anything.
User | Count |
---|---|
33 | |
16 | |
14 | |
9 | |
8 |
User | Count |
---|---|
50 | |
30 | |
26 | |
17 | |
13 |