I set up a Dataflow with a Destination to a Warehouse. That warehouse has a new schema. I want my Dataflow Destintion to CREATE a table in the new schema. I specify the new table name as <schema>.<table>. What I GET is a table in the dbo schema named dbo.<schema.table>.
Now, I can fix this nonsense with simple T-SQL commands so that the table is named appropriately and in the correct schema. I then accidently ran the Dataflow again without changing the Destination. I now have TWO tables in the database:
<schema>.<table> and dbo.<schema.table>. OK, my fault.
But if, at this point, I go back to the Dataflow to fix the destination and specify an EXISTING table in the Warehouse, I see TWO Object that *look* identical.
PLEASE make Warehouse Destinations in Dataflows such that it displays the table name AND schema name, AND make so that I am NOT forced to make New Table Destinations in the dbo schema. The New Table dialog option should allow you to specify the schema.
makromer
on:
Fabric Data Pipeline should be able to execute dbt...
on:
Customers should ereceive notifications for all th...
miguel
on:
Recent Data and Recent Connections
on:
Need more details on Average utilization% in Capac...
on:
Access Variable Library in Semantic Models
This is available today in all Fabric connectors that support schemas. You can read more about it from the official documentation in the link below:
Dataflow Gen2 data destinations and managed settings - Microsoft Fabric | Microsoft Learn