Forum Discussion
Fabric Data Warehouse
- Anonymous2 years ago
Hi HR_GN ,
I have tested it and when I select the “Enable staging” option it does not reproduce your error, it works fine. When I do not select the “Enable staging” option I can reproduce your error.
I have seen other users experiencing similar issues:
Difficulties with data from Lakehouse to Warehouse... - Microsoft Fabric Community
The reason for this issue is that some sources do not support the direct copy command, which requires staging. However, the performance message suggests disabling staging for better performance, leading to the conflicting messages you see.
You can try some workarounds:
- You can use Dataflow Gen2 in Fabric to move data from Lakehouse to Warehouse.
- You can use it by selecting the SQL endpoint corresponding to lakehouse at Explorer of Warehouse.
If you have any other questions please feel free to contact me.
Best Regards,
Yang
Community Support TeamIf there is any post helps, then please consider Accept it as the solution to help the other members find it more quickly.
If I misunderstand your needs or you still have problems on it, please feel free to let us know. Thanks a lot!
1. Workaround to copy from sql end points works and is faster and cost effective compared to other methods.
2. However for standardizing enterprose solutions, it still needs to work in Data Factory Copy Pipeline. Would this be fixed?
- frithjof_v2 years ago
Community Champion
You mention to copy from Lakehouse SQL Analytics Endpoint to Warehouse.
Please be aware of the potential for sync delays between Lakehouse and Lakehouse SQL Analytics Endpoint. Which means the Lakehouse SQL Analytics Endpoint may not expose the most updated data, in some cases.
https://www.reddit.com/r/MicrosoftFabric/s/MxRpxMBNUF