Data modelling issues in QV?

[#1]

Hi Guru's,

Please let me know what are the data modelling issues (apart from Synthetic key & Circular reference)  faced in QV?

Immediate responses could be appreciated.

Sree

[rustyfishbones]

Always check the Subset Ratios of Joins.

So if you are joining the Product Dimension Table to the Event Table Check the Subset Ratio to have a better Data Model, see below example, the Product Dimension linked to the Product Transactions has a Subset Ratio of 81%, which is not too bad, but ideally you want this at 100%, anything lower the 80% is a concern as you could be holding thousands of products that will have no transaction to select against

[Colin-Albert]

Another one to look for are tables that only have two fields - using a mapping load to bring the associated data into the parent table is more efficient.