|
Kristen
Test
United Kingdom
22191 Posts |
 Posted - 08/19/2010 : 04:11:37
|
If it was me I would make the databases the same as a first step.
Although its OK to have Version 1, Version 1.1, Version 1.2 etc. and then release Version 2.0
I would have the APP be able to "get" an XML file of all the updates to be applied, and use that to update the database.
A change script for all table / column DDL to modify the structure, and any SQL statements to modify data (such as set default values etc.)
I would have a table with the current Version Number, and another for a history of version changes that were run, and when.
The XML file could also "carry" new executables for the application and so no.
It would be easier if the computer could get its upgrades from a central source (i.e. across a network), but if that it not possible then you'll have to distribute them some other way - CDs if the target machines have CD/DVD drives |
 |
|
Master Upgrade Script
