Join us for an expert-led overview of the tools and concepts you'll need to pass exam PL-300. The first session starts on June 11th. See you there!
Get registeredJoin us at FabCon Vienna from September 15-18, 2025, for the ultimate Fabric, Power BI, SQL, and AI community-led learning event. Save €200 with code FABCOMM. Get registered
Hello Community,
I'm currently working on creating a data warehouse in Microsoft Fabric and have encountered a challenge with configuring collation settings. Specifically, I am unable to locate an option to specify collation settings to control case sensitivity, such as switching from case-sensitive to non-case-sensitive.
Could someone advise if there’s an alternative method or workaround to set the collation within Microsoft Fabric? Any guidance on managing collation settings effectively in this environment would be greatly appreciated.
Thanks!
Solved! Go to Solution.
Hi @AravindhRaju at the moment there are only 2 collations that you can use, and they are Warehouse-wide. You cannot specify different collations on tables/columns.
At the moment you'll need to use the API to create a Warehouse with case-insensitive (CI) collation - Latin1_General_100_CI_AS_KS_WS_SC_UTF8
How to: Create warehouses with case-insensitive (CI) collation - Microsoft Fabric | Microsoft Learn
You can also create a Warehouse using semantic link from a Notebook
Hi @AravindhRaju at the moment there are only 2 collations that you can use, and they are Warehouse-wide. You cannot specify different collations on tables/columns.
At the moment you'll need to use the API to create a Warehouse with case-insensitive (CI) collation - Latin1_General_100_CI_AS_KS_WS_SC_UTF8
How to: Create warehouses with case-insensitive (CI) collation - Microsoft Fabric | Microsoft Learn
You can also create a Warehouse using semantic link from a Notebook
I just came accross this while working on a similar issue:
Can't find my table in Warehouse (Case sensitivity... - Microsoft Fabric Community
How is it that the Warehouse table names are CASE SENSITIVE, but the Semantic Model built on top of that same Warehouse is NOT CASE SENSITIVE?
Turns out, you can have duplicate table names in a Warehouse if you build them in SSMS: dim_Date and dim_date can co-exist if created in SSMS, but only ONE of them will show up in the Semantic Models or if viewed via the Fabric browser experience.
Proud to be a Super User! | |
User | Count |
---|---|
2 | |
1 | |
1 | |
1 | |
1 |
User | Count |
---|---|
5 | |
3 | |
3 | |
2 | |
2 |