Hello Stijn, You are right, when using MEGA on a RDBMS (here SQL Server), a mirgation must be prepared to avoid any trouble with the data. A good way to secure this operation is to physically duplicate your environment in SQL Server. (you could also save the .mgr of your repositories and extensions of the environment before proceeding in the very unlikely case that there is a data loss during the process) Here are the steps to follow: 1. Ask the DBA to duplicate all the databases of your environment A MEGA database in SQL Server is named like this : <Environment name>_<Repository name>. The duplication must be made indicating for every copy a name with the new environment name* : <Environment new name>_<Repository name>. * (the reason for using a new name is that SQL Server does not allow many DB's with the same name). The SystemDb is the "root" repository of your environment, don't forget it. 2. Create the references for the new environment and its repositories For the following part, refer to the technical article « Repository - RDBMS Installation Guide MEGA 2009 SP5.pdf » - Using the same MEGA installed for production ( SP4 in your case ), follow what is indicated in the paragraph : « Restoring a Mega repository from formatted data ». Start with the « Restoring an environment (SystemDb repository) » part (using a new name for the environment to be restored. - When this is done, open Administration.exe then open the environment that you've just restored. - Right-click on the just-restored environment and click on the menu entry « Remove not referenced Repositories » so that you will be able to re-reference the environments repositories by restoring them too. - go then to the « Restoring a data repository » part and retsore every data repository of the environment following the paragraph's instructions. When this is over, you should have 2 identical environments referenced but with different names. - Delete the reference of the environment that has just been restored. - Open Administration.exe of the target MEGA version (SP5 R7 in your case). - Create a reference to the environment that was restored in the SP4. - Before you start the migration, you have to take care of the technical conversions of all the environment starting with the SystemDB (see paragrap « Handling of Mega RDBMS repositories specific internal format »). It meens that you will ignore all the messages inviting you to upgrade your environment before this step is complete. - you can now follow the steps for upgrading the environment edarolle
... View more
