Changes between Version 5 and Version 6 of BluePrint/DatabaseMigration


Ignore:
Timestamp:
06/17/12 10:13:58 (9 years ago)
Author:
Fran Boon
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • BluePrint/DatabaseMigration

    v5 v6  
    22[[TOC]]
    33== Work Flow ==
    4 === Primary: SysAdmin ===
     4=== Primary: SysAdmin of Server ===
    55The primary focus should be on supporting the SysAdmin whose job it is to keep production servers running.
     6* we can normally assume Linux servers, but should be as agnostic as possible
    67
    78They have a live system with live data & new code whose impact on the live data they are unaware of (we assume that the actual code has been tested separately with new data).
     
    3637* when the SysAdmin is confident that the migration has been tested sufficiently, they run the script with a different command line option to migrate the live system
    3738
     39=== Secondary: Offline Client ===
     40We have remote offline clients, primarily running on win32.
     41
     42We'd like to be able to ship them an update .exe which includes the new code & the tested(!) script to migrate the database.
     43
     44The migration script will be built by the release manager, so just needs to be run on the remote, however there is no tech support available locally so it needs to failsafe - it needs to test the migration & enable easy rollback of both DB & code if it encounters any unexpected errors.
    3845=== Secondary: Developer ===
    3946A secondary focus would be on supporting developers to provide hints to the SysAdmin about what how the migration should be done: