MSDAX Version Control System (VCS)

As many should know by now, Microsoft has introduced a version control tool within MorphX. This appears to be very practical while we'd want to track and manage all customizations brought into the development layer. However, a concern rose up once the development environment required a data refresh from the entire production database. Thus prior to refreshing, it is needed to offload the information from the following VCS tables:

• SysVersionControlMorphXItemTable
• SysVersionControlMorphXLockTable
• SysVersionControlMorphXRevisionTable
• SysVersionControlParameters
• SysVersionControlSynchronizeLog

Once backed up, proceed with the data refresh and load those five table back into DEV. And as much as the VCS can store a nice history of all your development into the previous tables, you will most importantly always have to check upon the SystemSequences table and make sure you update NEXTVAL with the next RecId of those five tables after completing the refresh. That should prevent the system from ever getting into a state of duplicates.