Subject | Exporting data from clients to a central database |
---|---|
Author | Diego Barros |
Post date | 2005-01-14T00:20:51Z |
Hi all,
I am working on an application that will be used by numerous clients. The records in each client's database need to be taken back to head office, where we have our main database, and where we will store all the data from all clients. This export process is done periodically.
What is a good approach to do this? I am thinking of setting up triggers which fire when inserts and updates occur. These triggers are placed on the tables which I want to transport back to head office. Each of these tables will have a date/time field, called LastUpdated, and this field is what the export process looks at to see which records have changed (or been inserted) since the last export.
Do this sound like a good (or at least) workable solution?
Regards,
Diego Barros
I am working on an application that will be used by numerous clients. The records in each client's database need to be taken back to head office, where we have our main database, and where we will store all the data from all clients. This export process is done periodically.
What is a good approach to do this? I am thinking of setting up triggers which fire when inserts and updates occur. These triggers are placed on the tables which I want to transport back to head office. Each of these tables will have a date/time field, called LastUpdated, and this field is what the export process looks at to see which records have changed (or been inserted) since the last export.
Do this sound like a good (or at least) workable solution?
Regards,
Diego Barros