Keys and Levels in MicroStrategy

Some notes and a tip:

Table keys are the lowest level attributes in their respective hierarchies that are present in the logical table.

Fact entry levels are the lowest attribute levels at which a fact exists. The fact entry levels correspond to the lowest-level table key attributes for all the tables that define the fact.

A fact is only extended if a join does not exist between a fact table and the attribute to which the fact will extend to, i.e. the fact does not exist at the level of that attribute.

MicroStrategy SQL Generation Engine is sensitive to differences between its internal state and the states of metadata objects, there is a risk of SQL generation failures if schema modifications take place during normal user activity. In general, it is not recommended to perform schema updates during periods of normal or high usage. Schema changes should normally be reserved for periods of little to no user activity.

Version control in MicroStrategy

MicroStrategy doesn't support Versioning. BTW, There are two types of versioning in MicroStrategy. Source control (what I'm taking about over here) and Slowly changing dimension (SCD). Lots of clients have put requests to MicroStrategy to have this feature of version control for schema object or at least attributes. In short the answer for this question is NO and I would never want MicroStrategy to have this features. Such a feature request is only idea that can come from bad MicroStrategy practice. Why in this world, do you want to have two definition. If a change in attribute breaks a report or sql goes haywire, one should rather fix this (that why it is job of MicroStrategy Architect). Such a feature would lead to lots of useless trial-n-error stuff in MicroStrategy. If you know any company who is behind this feature request, please post the name over here.

FYI, as per document ID (TN4100-800-0349), A current enhancement request exists for this functionality. Contact MicroStrategy Technical Support for the latest update of this request.

This would be a good feature for nuts in MicroStrategy and will give sane people hard time.

Update 13 Feb 2009

Cognos supports this feature. But one can't use different object(s) from different set of version. :-(