How do you main the version control in Microstrategy How do you main the version control in Microstrategy narenkv (Programmer) (OP) 18 Oct 02 06:30 I would like to know , How to maintain versions in Microstrategy is there anything i have to integrate the project with Microsoft sourcesafe Please let me knowThanksNAREN RE: How do you main the version control in Microstrategy JRO061601 (MIS) 18 Oct 02 08:53 While I realize not everyone is a native English speaker, it would help if you could ask your questions in complete and coherent sentences.I'm not aware of a way to integrate MicroStrategy with version control software. If you need to keep a version history, you can back up the metadata to different files periodically. Someone with more knowledge of this may want to weigh in on this topic. RE: How do you main the version control in Microstrategy chael (Programmer) 18 Oct 02 09:20 One of the practices that I have implemented is to have versions of metadata existing as projects. For example, you could have a version of a project for every 6 mos. Duplicating projects can be a little tedious, but worthwhile.Another option is to back up MD into an Access DB once a month or so. This should be in addition to the native DB backup strategies that you have (i.e. load MD to tape every night). The above refers to project versions. If you are interested in implementing versioning as a reporting perspective, it is a different issue. Please specify exactly what you are looking to do and we can be of more help.Chael RE: How do you main the version control in Microstrategy kwitkowski (Programmer) 12 Nov 02 09:32 We perform an Oracle export of the metadata twice a day. These exports are kept for 30 days and handles the 'oops' factor.When we promote a project from our development metadata to our production metadata, we make a copy of the project with the date as part of the project name (e.g. a copy of 'Project X' created today would be named 'Project X 2.11.12'. The copied projects are not registered in the Intelligence Server to reduce confusion, but are immiediatley available if needed.This is the best method I have found, please post if you come up with a better idea.