Forum Discussion

Element115's avatar
Element115
Icon for Memorable Member rankMemorable Member
2 years ago

BUG::New table in data warehouse not detected

STEPS 0__create a new data warehouse 1__create a new table in schema [dbo] (with column data types matching or compatible with on-prem SQL Server 2017 source) 2__wait, then refresh until table app...
Dataflows
frlunett's avatar
frlunett
Icon for Microsoft Employee rankMicrosoft Employee
2 years ago

Thanks for the quick reply.

 

I was referring to the refresh button highlighted in this UI:

 

For the slow refresh issue, would you be able to share the refresh session or request ID? You can find them in the Refresh history dialog:


I'm assuming both dataflows belong to the same workspace. In a scenario like this it might be worth disabling staging on the query that pulls the data from the first dataflow and writes the data into the output destination as the data is already in the staging Lakehouse (Data Factory Spotlight: Dataflow Gen2 | Microsoft Fabric Blog | Microsoft Fabric).

 



Element115's avatar
Element115
Icon for Memorable Member rankMemorable Member
2 years ago

So... DF2 eventually failed with a WriteToDataDestination.  Here are the 2 screenshots of the run result:

 

 

Still haven't been able to ingest properly data from an on-prem SQL Server DB using a DataFlow Gen2.  How is one supposed to do this?  Is it even possible???

 

Also, I read the blogs that are saying to open port 1433 on the machine that runs thePower BI data gateway locally.  So we did update the firewall rule according to the Microsoft help page on this topic just before this last attempt with 2 chained DataFlows.  And yet, it still ends in failure.