change-management-and-vault-moves

Replicating metadata structure changes in a new vault

When moving to a new vault, it is important to ensure that the metadata structure is replicated accurately to maintain the integrity of data and relationships. The MFSQL Connector provides tools and procedures to facilitate this process. The recommended approach is to first set up the new vault with the desired metadata structure using M-Files Admin or M-Files Desktop. Once the structure is in place, the procedure spMFDropAndUpdateMetadata can be used to drop and recreate the metadata structure tables in the SQL database to match the new vault. This ensures that the SQL tables are in sync with the new vault’s metadata structure. It is crucial to run this procedure before any data synchronization or updates are performed to avoid inconsistencies. After running the procedure, it is advisable to verify the metadata structure tables to ensure that all classes, properties, and relationships are correctly represented. In addition to the core synchronization procedures, it may be necessary to use the procedure spMFSynchronizeSpecificMetadata to update specific parts of the metadata structure if there are any customizations or specific requirements in the new vault. By following these steps and utilizing the provided procedures, you can effectively manage metadata structure changes when moving to a new vault, ensuring a smooth transition and maintaining data integrity.

warning:: text

The internal ids may not match When a new vault is created using replication in M-Files. If the MFSQL Database is created by restoring a backup of the source vault, then the metadata structure in the source vault and new vault may conflict. This means that the procedure spMFDropAndUpdateMetadata must be run to update the metadata structure tables in the new SQL database to match the new vault. Failure to do so may result in inconsistencies and errors during data synchronization.