Star Schema and Snowflake Schema? Why is it not a thing in DOMO?

verytiredgirl
verytiredgirl Member
edited October 17 in Other Ideas

It's a very common and even a recommended practice to do data warehousing design when you're analyzing/visualizing data but why is it not a thing in DOMO? It seems like you have to create 1 whole big and gigantic FACT Table every time you want to analyze something when you're working with an enterprise data level. And what makes it even worst is, most of the time, you don't just use 1 big and gigantic table for all the cards/visuals. Then you have to do ETLs to create say 5 big and gigantic tables for other cards.

Not to mention, the main reason why Star and Snowflake Schema are recommended over 1 Fact table is because well faster query performance and obviously a more structured data organization.

Tagged:
2
2 votes

Comments

  • DomoDork
    DomoDork Contributor

    I agree with this. Domo should have a feature, lets call it 'Magic Data Model' that works like MagicETL from a UI perspective, but is a way of connecting your inputs similar to Microsoft Analysis Services, Snowflake or any other snowflake style schema typically used in cubes. Then when it runs, it crunches through it, creating all the necessary slices of data and outputing it to a special type of dataset that cards and formulas can sit on top of. It would solve alot of problems when it comes to updating historical data, or restating historical just because a dimension changed etc.