Copy activity to lakehouse managed table with schema (Public Preview)

[VictorMed]

When using data pipelines with the copy activity into a lakehouse delta table (managed) with schema (public preview).

The activity generates a new schema with the table's name and stores the data as undefined.

Is this a known issue?

Thanks,

Victor

[Anonymous]

When defining a Lakehouse with a schema as the destination in a Copy activity within a Fabric pipeline, I encountered an error indicating that the dot (.) in the schema.table format is being recognized as part of the table name, which is not allowed.

How can I upload a table to a specific schema in a Fabric Lakehouse, rather than defaulting to the dbo schema?

[tkiwi]

Hi, I'm getting the same 'error' that a new schema is created with the tablename. Are there any news about this issue and if it will be fixed?

[Anonymous]

Hi @VictorMed ,

In response to your mention of whether this is a KNOWN ISSUE, I think it is, as other users have also reported this issue. When using the replication activity in the data pipeline to replicate data to the Lake Warehouse One Incremental Table, some users are experiencing the creation of a new schema with the name of the table and the datastore as undefined. You can refer to this link: Copying delta table from one lakehouse to another:... - Microsoft Fabric Community.

So I think you can use Azure data factory or Synapse pipeline. It seems it is currenly not possible via Fabric data pipelines.

Best Regards

Yilong Zhou

If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.