Forum Discussion

vasalari's avatar
vasalari
Icon for Helper I rankHelper I
1 year ago
Solved

Data warehouse Shortcut case sinsetivity

I have two data warehouses in two different workspaces. Using a shortcut linking DW2 and use it in DW1. The shortcut is created in a lakehouse. Things are working and I can access tables in DW2 from DW1. Both DWs are case INsinsetives but the lakehouse is       case sinsetive so I lose case sinsetivity of DW2.  Shortcut in Lakehouse changes the sinsetivity of source DW

 

  • Anonymous's avatar
    Anonymous
    1 year ago

    Hi vasalari ,

    Thank you for reaching out to the Microsoft Fabric Community forum and providing the details.

     

    In your scenario, this behavior is expected. Although DW1 and DW2 are case-insensitive, Lakehouses in Microsoft Fabric are case-sensitive by design. Therefore, when you create a shortcut in a Lakehouse to DW2, the Lakehouse's case sensitivity will apply, even if DW2 is case-insensitive. Currently, there is no way to inherit the source's case-insensitive behavior through a shortcut in a Lakehouse. To prevent such issues, it's recommended to use consistent casing for table and column names across all environments.

    Hope this helps. Please reach out for further assistance.

     

    Thank you.

     

  • Anonymous's avatar
    Anonymous
    1 year ago

    Hi vasalari  ,

     

    I wanted to follow up on our previous suggestions. We would like to hear back from you to ensure we can assist you further.

     

    Thank you.

4 Replies

  • Anonymous's avatar
    Anonymous
    Not applicable

    Hi vasalari ,

    Thank you for reaching out to the Microsoft Fabric Community forum and providing the details.

     

    In your scenario, this behavior is expected. Although DW1 and DW2 are case-insensitive, Lakehouses in Microsoft Fabric are case-sensitive by design. Therefore, when you create a shortcut in a Lakehouse to DW2, the Lakehouse's case sensitivity will apply, even if DW2 is case-insensitive. Currently, there is no way to inherit the source's case-insensitive behavior through a shortcut in a Lakehouse. To prevent such issues, it's recommended to use consistent casing for table and column names across all environments.

    Hope this helps. Please reach out for further assistance.

     

    Thank you.

     

  • Anonymous's avatar
    Anonymous
    Not applicable

    Hi vasalari  ,

     

    I wanted to follow up on our previous suggestions. We would like to hear back from you to ensure we can assist you further.

     

    Thank you.

  • Anonymous's avatar
    Anonymous
    Not applicable

    Hi vasalari ,

     

    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.

     

    Thank you.

  • I honestly believe Fabric was released too early.  regular stuff from SQL is missing.  as simple as creating atable with default value for a field.    I hope MS can implement shortcut from warehouse