Can't find my table in Warehouse (Case sensitivity)

[ToddChitt]

I built my date dimension as "dim_Date". It was later 'decided' (and much to my chagrin) that we needed to use 'snake case' for all tables in the gold layer of the warehouse (and for the semantic model). So "dim_Date" needed to become "dim_date". Not hard. Warehouses are CASE SENSITIVE collation so the two tables can live side-by-side in the same warehouse until I get all relationships moved over etc. I created the new table dim_data and populated it with about twice as many dates as the original. Using SSMS I can see the two tables. In the Warehouse view in Fabric, I can query the two tables independently and see different result counts.

But in my new Semantic Model (not the Default), the new tables does not show up. If I click Edit Tables so that I can add the new dim_date to the model, it is not there. I can search for "dim_date" and this is what i get:

If the Warehouse is going to be CASE SENSITIVE for table names, then the Semantic Model interface needs to be as well.

I see this as a BUG.

[Anonymous]

Hi @ToddChitt ,

Thanks for the reply from Srisakthi .

Although you mentioned that Data Warehouse is case-sensitive sorting rules, it reports an error when creating a table using a naming rule that is case-sensitive but has the same name:

In your problem description, I see that you created “dim_data” instead of “dim_date”, try searching for “dim_data” table.

Regarding your comment “If the Warehouse is going to be CASE SENSITIVE for table names, then the Semantic Model interface needs to be as well”, I think you can comment on Home .

If you have any other questions please feel free to contact me.

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!

[ToddChitt · Accepted solution]

Hello @Anonymous 

dim_data was a type on my part. Yes, it was actually created as dim_date. I looked at this several different ways: Default Semantic Model, new Semantic Model based on the Warehouse, and every time I went looking for the lower case table, it couldn't be found. Turns out this is a known issue:

Known issue - The Data Warehouse Object Explorer doesn't support case-sensitive object names - Microsoft Fabric | Microsoft Learn

In the end, I dropped dim_date, then did EXEC sp_rename to get dim_Date renamed to dim_date2, then from dim_date2 back to dim_date. (It would NOT support going from dim_Date to dim_date because those are technically the same name if you disregard case). 

Unfortunately, after almost a year of using this tool, there is still a steep learning curve and basic issues that I falter over.

[Anonymous]

Hi @ToddChitt ,

Glad you found a workaround, although the process is tedious.

Could you please mark this helpful post as “Answered”?

If others in the community are experiencing the same problem as you, this will help them find a solution easily.

Thank you for your cooperation!

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!

[Srisakthi]

Hi @ToddChitt ,

When i try to replicate the same scenario, it is not allowing me to even create a table with same name . I'm getting the below error. Earlier it allowed us to create name with case sensitive. But now it has been fixed in warehouse as well. Can you please check once again.

Regards,

Srisakthi