Progress
Developer’s Toolkit
Upgrading with Time-stamp-based R-code Files
If database changes are extensive, you might choose to distribute brand new versions of your application and the database. If you plan to distribute the precompiled version of an upgraded database, follow these steps.
Your users will have to dump their data from the old database and load it into the new database. Therefore, you must also provide your users with a dump/reload facility. If you are changing any of the file formats used in your application, you must modify the set of load files to work with those new formats.
Once this is done, follow these steps:
- Run the mkdump script against the new version of the database.
- Supply a modified set of file load procedures so the user can reload the database using procedures that are compatible with the old data format. These procedures will probably be different from the file load procedures the user will use to reload the new database after dumping it.
- Supply new file dump, file load, and subdirectory procedures so the user can later dump and reload the database, if necessary.
If you are making database modifications and you are supplying new dump and reload procedures, the user must do the following:
NOTE: You can use the binary dump and load to reduce this time dramatically. See the section on PROUTIL in the Progress Database Administration Guide and Reference for more information on binary dump and load.- Use the old dump procedure to dump the data in the existing database. (Note that dumping and reloading a large database might take days, depending on the database size.)
- Make a copy of the new basic database.
- Use the new load procedure to load the old database data into the new database. You must ensure that the new load procedure is prepared to accept data in the format and order dumped by the old dump procedures.
Copyright © 2004 Progress Software Corporation www.progress.com Voice: (781) 280-4000 Fax: (781) 280-4095 |