Refreshing data on a test database
Posted in 1997
Our users have a requirement for a test database, with the data regularly
refreshed from production. We achieve this by dbexporting the production
database, dropping the test one then using dbimport to re-create it.
The users are beginging to have their own stored procedures and triggers
developed, and do not want to lose these. To continue to provide them with a
data refresh whilst preserving other database items I have thought of the
following methods:
1. Unload each table from production, cleardown from then load into the
corresponding table on the test database.
2. Unload the procedures and triggers on the test database, use the
dbexport-drop-dbimport as at present, then re-load the procedures and triggers.
Neither seems well-suited to a regular, scripted process. Any other ideas?
Thanks
Neil Truby
Chase Manhattan Bank
Bournemouth, UK