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. 
本文讨论了MicroStrategy不支持版本控制的原因及潜在影响,并对比了Cognos的相关特性。作者认为版本控制可能会导致不必要的试错行为,建议直接修复报告或SQL问题。

871

被折叠的 条评论
为什么被折叠?



