I regularly have to take in large volumes of data that are not normalized, and then spend time reducing their size and storage requirements by simplifying them. What I would like to see is some intelligent functionality that can analyse a table to identify columns that should be normalized, and then when selected can be split out to a separate reference table with a reference key which can be added to the source table. As this needs to handle data refreshes, it should be encapsulated in the M language steps for data loading. It should be simple enough for non-experts to use.
1 Comment
- fbcideas_migusrNew MemberStatus added:New
Recent ideas
OneLake Catalog full-text and content search
Why is it not possible to search OneLake by item description or even content? So I was thinking about how a user can find a table if they don't know in which lakehouse it is located? Why can't you se...TePe12 hours agoHelper IVPlanned1.1KViews21likes5Comments