BUG Copy Activity Fabric UPPERCASE

[Mattiar]

Hello, everyone,

I wanted to report a bug found in the copy data of a pipeline in Fabric. In my specific case, I am reading the query from a json where I have for example a SELECT Pippo, Pluto, Paperino FROM disney.user

The output that returns me error obviously being case sensitive, is that all in uppercase. Basically it's like the query has become: SELECT PIPPO, PLUTO, PAPERINO FROM DISNEY.USER.

Obviously this gives me an error telling me that the column PIPPO does not exist.

[Anonymous · Accepted solution]

Hi @Mattiar 

Based on the information you provided, I surmise that this is related to the case sensitivity of SQL queries in Fabric pipes.

You can try using double quotes around column names in SQL queries. This should preserve the case sensitivity.

Regards,

Nono Chen

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

[Anonymous · Accepted solution]

Hi @Mattiar 

Based on the information you provided, I surmise that this is related to the case sensitivity of SQL queries in Fabric pipes.

You can try using double quotes around column names in SQL queries. This should preserve the case sensitivity.

Regards,

Nono Chen

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

[Mattiar · Accepted solution]

I had tried square brackets and it did not work. I have now tried double quotes (with the escape character since I read the query from a json) and the / prefixed by escape and everything finally worked.
Great.

[Anonymous]

Hi @Mattiar 

Thank you for your feedback and glad to hear that you have resolved the issue.

If you have any questions, please continue to post in this forum.

Regards,

Nono Chen

[Mattiar]

Of course.

I show you the result of the variable set before and the one that reads the copy data instead:

this step is correct and the source of copy data is correct too:

and now the wrong result:

If I write select * from, it obviously works.

[richbenmintz]

I think you issue/bug is with the SAP Hana Connector converting the query to uppercase, can you test this by using a static query, with the lowercase column names and seeing if the connector modifies that.

[Mattiar]

Yes it is most likely related to that, but that does not detract from the fact that it is an infrastructure bug. I wanted to expose the problem so that someone who can edit that, knows the bug and fixes it.

[richbenmintz]

Hi @Mattiar, 

I am simply trying to highlight for @Anonymous, that the behaviour is likely related to the source type, as they are trying to replicate your issue using a lakehouse source.

[Mattiar]

Yes yes, no problem, in fact I thank you for the added value you gave. 👍

[Anonymous]

Hi @Mattiar 

I tested your problem and found no errors.

Can you provide some configuration screenshots and error messages? This helps us solve the problem.

Regards,

Nono Chen

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