Hi, It would be great to have lakehouse and warehouse support different collations, specifically case sensitive and case insensitive. At the moment we are able to create objects that are n...
greg30
3 years agoNew Member
I see case-sensitivity in areas of Fabric as a serious mistake, particularly given the target audience.
https://blog.greglow.com/2018/01/23/opinion-case-sensitivity-pox-computing/
It's not just case sensitivity though. One thing that Fabric could have been is a unifying experience, yet today, each part of it has diferent rules for naming, etc. This should not have occured. It is a lost opportunity to make things easier for users.
Recent ideas
Allow NotebookUtils getSecret() to authenticate with Workspace Identity
Current behavior In Microsoft Fabric, notebookutils.credentials.getSecret() authenticates against Azure Key Vault using the identity of the user who executes the notebook. This behavior appli...tmihara1 hour agoNew MemberNew16Views1like1CommentAllow us to rename fabric data agents published to m365
If we use deployment pipelines to promote fabric data agents between dev, test/UAT, and prod fabric workspaces, we need to keep the name of the fabric agent the same in each workspace. If we want to ...PeterDaniels8 hours agoAdvocate IIINew185Views0likes2CommentsMake workspace and item session persistence optional
Description The new persistent session behavior in Microsoft Fabric should be optional rather than forced. Currently, Fabric remembers the workspaces and items that were open in my previous session...TeemuMultanen9 hours agoAdvocate INew299Views47likes2Comments