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
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.