topic Re: Data Flow Gen 2 : Data Destination = Warehouse connection error in Data Warehouse

Data Flow Gen 2 : Data Destination = Warehouse connection error

aathmer — Mon, 19 Feb 2024 22:40:31 GMT

I get this error after selecting Data Destination = warehouse in Data Flow Gen2 -

An exception occurred: The given data source kind is not supported. Data source kind: Warehouse.

When I read in data from the Warehouse in my Fabric workspace, I get no error when choosing Data Destination = warehouse.

When I read in data from my Synapse Data Warehouse, or my SQL Server database, I get the error above - data source kind not supported.

What am i missing, and what should I do differently to make this work ok.

Re: Data Flow Gen 2 : Data Destination = Warehouse connection error

NandanHegde — Tue, 20 Feb 2024 04:17:56 GMT

Hey,

Can you please specify whether the warehouse that you are trying to map to the destination is a fabric warehouse and not a synpase workspace database?
And are your dataflow gen 2 and fabric warehouse in same workspace?

Re: Data Flow Gen 2 : Data Destination = Warehouse connection error

aathmer — Tue, 20 Feb 2024 16:09:38 GMT

Thanks for replying Nandan - the warehouse I'm trying to map to the destination is a SQL Server database in our Azure environment (previously on-prem).

The warehouse is local to the fabric workspace that also contains the Gen2 DataFlow. The error occurs when the connection is being validated - in the bottom left it says - creating connection - validating connection and then the error message occurs.

Hope this helps - something to do with connecting that is different when the input data is from SQL Synapse not Fabric warehouse.

Re: Data Flow Gen 2 : Data Destination = Warehouse connection error

NandanHegde — Tue, 20 Feb 2024 16:15:40 GMT

Hey, unfortunately as of now Dataflow Gen 2 only supports 4 destinations and the databases supported are only:

1) Azure SQL Database

2) Actaul fabric warehouse

SQL Server databases on IaaS is not supported

Re: Data Flow Gen 2 : Data Destination = Warehouse connection error

aathmer — Tue, 20 Feb 2024 16:32:47 GMT

Thank you Nandan - I'm ingesting data into the Dataflow Gen 2 from the SQL Server - and that works fine.

Then when I select warehouse from the destination options, it fails with the error message above.

When I ingest data from the warehouse inside the Fabric workspace and select warehouse as destination, it works fine - I can copy data into a new table that way.

I'm selecting warehouse as destination - and then get the error. Thank you for help on this Nandan - I cannot figure out what i need to do next.

Re: Data Flow Gen 2 : Data Destination = Warehouse connection error

HimanshuS-msft — Wed, 21 Feb 2024 18:42:12 GMT

Hello aathmer ,

Just trying to reinterate the point which NandanHegde calledout before . At this time the below destination are supported by DF Gen2 and since the destination SQL Server database in our Azure environment (previously on-prem) is still not supported so you are getting the error .

Please add this is as a feature ask for the Product team here : https://ideas.fabric.microsoft.com/?view=new

Thanks
Himanshu

Re: Data Flow Gen 2 : Data Destination = Warehouse connection error

aathmer — Wed, 21 Feb 2024 20:58:45 GMT

Yes thank you Himanshu I will add to the feature request although I have no current need to write out to SQL Server using Dataflow Gen2.

The Azure / Fabric admin has also updated the Azure Gateway and as a result the error has gone away and I now get prompted for the Fabric warehouse to use as destination. It then fails again with an error that I now know indicates that the firewall on my SQL Server is too restrictive - which the Azure / Fabric admin will address.

So I think in the next week or so I will be able to successfully read from SQL Server and write to the Fabric warehouse using Dataflow Gen2 - which is my goal.

Thanks again for your help.

Re: Data Flow Gen 2 : Data Destination = Warehouse connection error

HimanshuS-msft — Thu, 22 Feb 2024 17:38:38 GMT

aathmer : Thanks for writing back , if I were you i could have accepted NandanHegde response as a solution , that way we could consider this thread to be closed .

Good luck .