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

From our telemetry it does seem like a gateway connectivity issue. Can you check the error message that's shown when you click on the Sector_TS_* activity from the refresh history dialog?

 

We do have a blog post that describes limitations and considerations when using Data Gateway with output destination in the context of Dataflow Gen2: On-premises data gateway considerations for data destinations in Dataflow Gen2 - Microsoft Fabric | Microsoft Learn

 

Finally, it is by design to disallow publishing a dataflow that only contains queries that are not marked as staged nor have an output destination set.

 

Thanks,
Frank.

Anonymous's avatar
Anonymous
Not applicable
2 years ago

Hello Element115 ,

We haven’t heard from you after the last response by frlunett - and was just checking back to see if you have a resolution yet .
In case if you have any resolution please do share that same with the community as it can be helpful to others .
Otherwise, will respond back with the more details and we will try to help .

  • Anonymous's avatar
    Anonymous
    Not applicable
    2 years ago

    Hi Element115 ,

    We haven’t heard from you after the last response by @frlunett - and was just checking back to see if you have a resolution yet .
    In case if you have any resolution please do share that same with the community as it can be helpful to others .
    Otherwise, will respond back with the more details and we will try to help .

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

      Apologies, I got sidetracked by all the support tickets opened for the other bugs that popped up when using a lakehouse to ingest data from the on-prem DB.  Let's put the data warehouse on hold for now, as our scenario benefits more from a lakehouse anyway and let's see if support manages to find a solution to the issues blocking  not only ingestion from on-prem, but also from a lakehouse source. 

       

      Here is to hoping that the new OPGW will solve all these issues and allow bulk data copy from an on-prem DB to a lakehouse using a simple pipeline.