VPN Rollout Implications to MK ERP Instances
The last discussion we had with regard to how MK can accomodate the upcoming VPN links to Malaysia, Thailand and Singapore indicate that a detailed study is suggested to evaluate possibilities of running two separate instances of the MK server - one on the new MK server, one on where it is today.
A big-bang approach to switch overseas offices onto the new MK instance is not recommended due to the inherent risk we face when it is performed simulataneously. Due to the way the MK database schemas was first designed, tables within the database are commonly accessed by the different business entities in CEH. Hence, a slice and dice approach to systematically migrate site-specific database is not possible.
The only recommendation to all existing constraints is to ensure two (AS-IS and TO-BE) instances are kept synchronized (accuracy discrapancies can increase during the migration process period) while individual office sites are systematically switched over to the new MK instance.
An observation period of approximately 2 weeks will be given to each site after the switch, whereby the existing contract be terminated upon the dust settling down for each location. Based on Mr. Sim's planned schedule, all six sites can be systematically switched over in 2.5 to 3 months period from today.
Updated by Lawrence