Early Versions (SQL Server 2000 – 2008)

You'll need to plan carefully when dealing with monster dimensions because they consume large amounts of maintenance time and CPU cycles. You can manage rapidly changing monster dimensions by splitting the stable and hot attributes and then linking them through a fact table. You can also manage rapidly changing monster dimensions by banding the hot attributes, which is where you create a set of non-overlapping value ranges for each rapidly changing attribute.

byMichelle A. Poolet