Right now for SMEs we have a separate table than corporate. We envisage doing same if we use MemSQL.
Corporate table is full Star Schema whereas SME table is more 3NF event model. So the SME table has an unique event-id in addition to all fields in Corporate table; and additional use cases of -
(1) querying on event-id and
(2) sometimes updates using event-id when there is any event correction.
Having a separate SME table gives us flexibility to have different table design if that is more performant - especially given the fact that it won't fan out as SME user has only a few outlets access therefore 1-2 partitions are accessed only.
This is related to https://github.com/sudsk/memsql-perf/issues/1
Right now for SMEs we have a separate table than corporate. We envisage doing same if we use MemSQL.
Corporate table is full Star Schema whereas SME table is more 3NF event model. So the SME table has an unique event-id in addition to all fields in Corporate table; and additional use cases of - (1) querying on event-id and (2) sometimes updates using event-id when there is any event correction.
Having a separate SME table gives us flexibility to have different table design if that is more performant - especially given the fact that it won't fan out as SME user has only a few outlets access therefore 1-2 partitions are accessed only.
What do you suggest for designing SME table?