Ferdipux,

Велозавод это не эталон, а показать, что так можно сделать.

1. Do use numeric keys for attributes that contain many members (>1 million)

2. #4: Use Integer Data Type for Attribute Keys If at All Possible
For best processing performance, try to use the smallest data type for attribute key columns. Although you could use string data types for key columns, they do not perform nearly as well as the numeric data types. At times you may need to use multiple columns for the composite key for a dimension attribute. Although this practice is almost always acceptable, for large dimensions (and particularly for fact level dimensions) you may have to add an alternate key to the dimension table to ensure processing is efficient. For example, let’s suppose you have a fact level “transaction” attribute and you use company identifier, effective date, and journal entry identifier string columns as keys for this attribute. While processing this dimension, MSAS must retrieve a unique combination of three string columns, which can be very time-consuming for a dimension that contains millions of records. Instead, you can add an identity column (or another integer column uniquely identifying each transaction) to the dimension table and use it as the attribute key. Reading a single integer column will be considerably faster than reading three string columns. Storing integer keys will also be much more efficient.