topic Re: Copy Data failure to lakehouse: sql server column names with spaces in Pipelines

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

msprog — Tue, 16 Sep 2025 00:39:59 GMT

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

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

lbendlin — Tue, 16 Sep 2025 01:13:48 GMT

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

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

Anonymous — Wed, 12 Nov 2025 10:23:02 GMT

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 to -> Default_Create_Configuration_Code

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

Try updating to the latest gateway version (v3000.286.14) and test again.
If you are still unable to solve the issue you can reach out to Microsoft Support by raising a ticket with Microsoft Support.

Please refer below link on how to raise a contact support or support ticket.
How to create a Fabric and Power BI Support ticket - Power BI | Microsoft Learn

Regards,
Sreeteja.

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

Anonymous — Mon, 22 Sep 2025 09:16:56 GMT

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.

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

Anonymous — Tue, 30 Sep 2025 04:51:55 GMT

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

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

Anonymous — Mon, 06 Oct 2025 05:12:49 GMT

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

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

ForwardArsenal7 — Thu, 09 Oct 2025 05:52:05 GMT

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

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

Anonymous — Thu, 09 Oct 2025 06:03:21 GMT

Hi ForwardArsenal7 ,
Thanks for your update.

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

msprog — Thu, 09 Oct 2025 06:09:04 GMT

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

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

Anonymous — Wed, 12 Nov 2025 10:27:36 GMT

Hi msprog ,

Could you please confirm if the issue has been resolved after raising a support case? If a solution has been found, it would be greatly appreciated if you could share your insights with the community. This would be helpful for other members who may encounter similar issues.

Thank you for your understanding and assistance.