Copy Data failure to lakehouse: sql server column names with spaces

[msprog]

we have an onprem sql server, In Fabric, a gateway connection is configured to the server. 

Now I have a pipeline with a Copy Data configured with source as this sql server and target  as the fabric lakehouse. 

Some of the sql tables have space in the column names and the Copy Data fails saying 

Failure happened on 'destination' side. ErrorCode=DeltaInvalidCharacterInColumnName,'Type=Microsoft.DataTransfer.Common.Shared.HybridDeliveryException,Message=Column name Default Create Configuration Code contains invalid characters. ",;{}()\n\t=" are not supported.,Source=Microsoft.DataTransfer.ClientLibrary,'

anyone faced this issue before please suggest

thanks

[lbendlin]

That is a well known limitation. Remove the spaces from the table names and column names.

[v-sshirivolu]

Hi @msprog ,
Thank you for reaching out to the Forum community.

This error occurs because Fabric Lakehouse (Delta tables) does not permit spaces or special characters in column names. To fix it try In the Copy Data activity, navigate to the Mapping tab. Map the source columns to target columns using valid names (replace spaces with underscores or remove special characters).
Example: Default Create Configuration Code -> Default_Create_Configuration_Code

Alternatively, you can use a SQL query or view to rename the columns before copying.

Regards,
Sreeteja.

[v-sshirivolu]

Hi @msprog ,

I hope the information provided above assists you in resolving the issue. If you have any additional questions or concerns, please do not hesitate to contact us. We are here to support you and will be happy to help with any further assistance you may need.

[v-sshirivolu]

Hi @msprog ,

I hope the above details help you fix the issue. If you still have any questions or need more help, feel free to reach out. We’re always here to support you

[v-sshirivolu]

Hi @msprog ,
I wanted to check if you had the opportunity to review the information provided. Please feel free to contact us if you have any further questions

[ForwardArsenal7]

The latest release of OPDG (version 3000.286.14) addresses this issue. Please download it here. 

[v-sshirivolu]

Hi @ForwardArsenal7 ,
Thanks for your update.

[msprog]

thanks @ForwardArsenal7  please can you point me to any doc that says it is addressed please. just wanted to see the features in the .14 release pls, so i can take it to my stakeholders. thanks