Subject | Syncronizing Databases |
---|---|
Author | Todd Brasseur |
Post date | 2001-08-13T17:45:24Z |
We are trying to decide how to handle keeping our clients databases
metadata the same as ours.
We have a production database in our office which we are continually
changing as our product evolves. Our clients have their own copies of
the database with their data.
Every once in a while, we give them a new 'release of the software'
which includes the new program along with updates to the database. We
are finding it quite alot of work to maintain 'change scripts' to run
against our clients databases. The most work is in keeping track of
which scripts have been run against which clients databases.
Does anyone have a similiar situation? Any ideas regarding how to
manage the database changes would be greatly appreciated.
Todd Brasseur
COMPASS Municipal Services Inc.
metadata the same as ours.
We have a production database in our office which we are continually
changing as our product evolves. Our clients have their own copies of
the database with their data.
Every once in a while, we give them a new 'release of the software'
which includes the new program along with updates to the database. We
are finding it quite alot of work to maintain 'change scripts' to run
against our clients databases. The most work is in keeping track of
which scripts have been run against which clients databases.
Does anyone have a similiar situation? Any ideas regarding how to
manage the database changes would be greatly appreciated.
Todd Brasseur
COMPASS Municipal Services Inc.