Forum Discussion
Writing to a specific warehouse schema using a dataflow gen2
tayloramy pmscorca we implemented the capability of writing to a given schema in Azure Sql, Lakehouse, Warehouse and Fabric Sql quite some time ago already.
As mentioned by miguel you need to ensure that you expand Advanced option when selecting the connector and set "Navigate using full hierarchy" to True.
Once done, on the next stage you'll be able to see the list of schema you can write to
Best regards,
Antoine
tayloramy pmscorca we implemented the capability of writing to a given schema in Azure Sql, Lakehouse, Warehouse and Fabric Sql quite some time ago already.
As mentioned by miguel you need to ensure that you expand Advanced option when selecting the connector and set "Navigate using full hierarchy" to True.
Once done, on the next stage you'll be able to see the list of schema you can write to
Best regards,
Antoine
Hi anros
I'm referring when it occurs creating a new table (also if the "Navigate using full hierarchy" option is set to True): it isn't possible to specify any destination schemas. For me, this issue isn't solved!
I'm not sure I'm following. The schemas are in the left where you can pick them like perhaps db_datareader. Once that schema is selected you can input the name of a new table in then input box in the right.
what is the issue that you're seeing?
Hi, at the left of the input box where I can write the name of the table to create I don't see any input boxes for the related schema name.
While it's great that it's possible to write to different schema, are there any plans to default 'navigate using full hierarchy' to true? Having to expand and set this every time you select a data destination adds unnecessary overhead when it's likely that data shouldn't be written to just dbo schema a lot of the time. I don't see a reason why this shouldn't be enabled by default all of the time or any benefit to not doing this
OMackenzie this is something we will actually release very soon 😉
