http://s-and-j.co.uk/wiki/index.php?action=history&feed=atom&title=Data_migration_go-live_strategy 2026-09-18T13:11:39Z Revision history for this page on the wiki MediaWiki 1.44.0 http://s-and-j.co.uk/wiki/index.php?title=Data_migration_go-live_strategy&diff=115&oldid=prev 2017-06-15T20:45:21Z

<p>Recreated page</p> <p><b>New page</b></p><div>* Q1. How will the business cut-over(s) occur?<br /> : Will it be phased, pilot, parallel running or &lt;shudder&gt; big bang?<br /> <br /> * Q2. Can / will transitional storage be used?<br /> : Will data be held in a temporary storage areaa while it is manipulated annd transformed, requiring down-time by the business (e.g. big complex databases of transactional data from one provider&#039;s system to another)? Or can it be carried across in one transaction (e.g. mirroring &amp; switch-off, or changing the IP address of a server or a drive mapping)?<br /> <br /> * Q3. Will data synchronisation be required?<br /> : Will it be necessary to keep two live systems synchronised during the migration, for example as a multi-database application is migrated piecemeal? And if so, will it be unidirectional or bi-directional? Relevant to phased, pilot and parallel running.<br /> <br /> * Q4. How much downtime can be tolerated?<br /> : Bearing in mind testing will be required during that down-time. Parallel running allows plenty of testing.<br /> <br /> <br /> [[Category:Data migration]]</div>

Simon