Lakehouse SQL analytics endpoint collation is not correct

Hi will-trickett ,

In the SQL endpoint of Fabric lakehouse, the default is case-sensitive.

If you only specify a collation for a column, when you create a view and query the view, that column follows the collation you specify, while the other columns use their own default collation. So, if you only specify a collation for one column, the other columns may still be case-sensitive when querying the view.

To ensure that the entire table is case-insensitive, it's a good idea to assign the same collation to all relevant columns when you create the table, or explicitly specify a collation for each column in your query.

In addition, collates can only be used for character data types (e.g., char, varchar, nvarchar, and text), not numeric data types (e.g., int, float, decimal, etc.).

Best Regards,
Yang
Community Support Team

If there is any post helps, then please consider Accept it as the solution  to help the other members find it more quickly.
If I misunderstand your needs or you still have problems on it, please feel free to let us know. Thanks a lot!