I cloned a test environment from the production environment and I have installed the maintenance pack in the test environment. Now I have two ways to apply the maintenance pack to the environment, the one is installing the packages to the production directly as I did like in test environment, the one is importing the new data from production environment to the test environment and then clone the test environment as the production environment. Can anybody tell me which one is choose mostly in your project? Or is there any other better way?
Yes, we can apply it to PROD like did for test environment. But it may take too much time that customer can’t use the system until we finished it. In my opinion, it’s not very good.
And what’s the major step in your upgrade project? How to migrate and solve the error of the customized development when upgrade?
Edited by: hzg on Apr 16, 2013 9:49 AM
I would always prefer to apply the Maintenance Pack in Prod after it is applied in DEMO, DEV, TEST, UAT. After applying the maintenance packs in DEV or any envt, Dev team might have to retrofit some errors or codes. Those things you can migrate later after the Maintenance Packs application and composite project.
According to me, every step is important while applying the MP ( be it copy project, running DMSs, Data conversion, copying the file objects ). Let me know if you have any other questions.