Data warehouse modelling on Vertica
I heard from a lot of people that it's good to have wide, fat tables that have every piece of information in Vertica. My question is: Is it true? And does that mean that we actually don't need to care about snowflake/star schema any more?
The frustration comes when I can't tell "good" flat tables from "bad", "lazy" ones. It seems that our BI tends to use really wide tables with 100 columns, and whenever we want to connect two stuffs (let's say we have a new feature, and we want to connect the purchase of this new feature with the virtual commodities obtained), they will just add a new connection id, and the table becomes one more column wider.
Is this a good practice? I highly doubt this is the case. But I'm not familiar with the internals of Vertica (TBH you guys don't publish enough material/books for this topic, just look at the number of books on say SQL Server, but I guess it's the normal of all big-data stuffs) so I really can't make proper judgement.
What's your thought on this? Is DWH still a thing in Vertica?