Recently wanted to pull in hundreds of tables from an on-prem DB.
I want to put them into a (new) schema in a Lakehouse.
I do NOT want to type/paste in the schema for each of hundreds of tables. There should be a better way to do this.
If there already is a better way to do this, it should be more obvious in the UI for people like me π
Even allowing us to modify the JSON for the Copy Job would be helpful because I could copy out the JSON, run some code against that to update the destination schema for each table and plop the JSON code back into the Copy Job. But, it looks to be read-only.
No CommentsBe the first to comment
Recent ideas
File level commit - Need the ability to edit the commit description
I tried the recently announce file level commit for Fabric items. One notable issue I have with the feature (testing this with a Fabric warehouse, I'm assuming this would hold true for other items): ...DataBard9 hours agoMost Valuable ProfessionalNew36Views0likes3CommentsFabric Deployment Pipeline Should Automatically Preserve or Upgrade Semantic Model Compatibility
Category: Microsoft Fabric β Deployment Pipelines | Semantic Models | Direct Lake The Problem When deploying a Direct Lake semantic model containing calculated columns or calculated tables throug...Murtaza_Ghafoor1 day agoSuper UserNew4Views0likes0Comments