Forum Discussion
Problem to import on premise data onto a lakehouse using a DataflowGen2
- 2 years ago
Hi alfBI
Thanks for using Microsoft Fabric Community.
As I understand that you are trying to load data from an on premise SQL Server onto a Fabric lakehouse using a Dataflow Gen2.
In scenarios where your data sources are located on-premises, Microsoft provides the On-Premises Data Gateway to securely bridge the gap between your on-premises environment and the cloud. This document will guide you through the process of accessing on-premises data sources within Data Factory for Microsoft Fabric using the On-Premises Data Gateway.
For more details please refer to the below mentioned links:
Install an on-premises data gateway.
How to access on-premises data sources in Data Factory for Microsoft Fabric.
On-premises data gateway considerations for data destinations in Dataflow Gen2.
I hope this information is helpful. Please do let us know if you have any queries.
Hi,
Effectively there was a problem on the config file "Microsoft.Mashup.Container.NetFX45.exe" never noticed before until now (we have started to use the gateway to load dataflows).
Once fixed we are finally to connect lakehouse to destination, (but with lot of patience, the message below "Validating Connection" appeared during more than 2 minutes....
once completed, navigation across workspaces to reach the lakehouse was extremely slow and once the lakehouse was selected it took a long time to create the table (> 2 min).
So, more than 5 min only to have the dataflow ready......Finally despite the fact that the dataflow was published following error does appear when executed
What are we doing wrong here? Access to *.datawarehouse.pbidedicated.windows.net is already enable on our firewall...... Sounds we are each time closer but not enough 🙂
Many Thx
- dazhang2 years ago
Microsoft Employee
Hi Alfons,
"The value is not updateable" is an issue that we just published a fix for today, would you mind upgrading to the latest version of the on-premises data gateway (3000.198.17) and try refreshing your dataflow again?
Thanks,
David