Kbase 155: How to use the Incremental Dump Routine in Version 6
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
5/10/1998 |
|
How to use the Incremental Dump Routine in Version 6
910625-cmb01
INTRODUCTION:
=============
This Product Services Technical Support Knowledgebase entry explains
how to do an incremental dump of your Version 6 database.
WHY YOU NEED TO DO THIS:
========================
When you first create your database and add all the files and fields,
it is good practice to make a copy of that "basic" database (without
any data) so you have a backup of the schema. This is helpful
if you plan to distribute your database to customers. You should
have a copy of the schema so you can make changes for the customer.
You can then use the Incremental Dump Routine to log the changes
between your database and the customers. These changes can then
be applied to the customers database.
PROCEDURAL APPROACH:
====================
Use the following steps to perform an incremental dump of your
Version 6 database:
To Create the Incremental Dump file:
------------------------------------
A. You need two databases:
1. The customer's copy of the database (before any changes).
2. The "revised" database (with schema changes).
B. Connect to the "revised" database first. This database is the
developer's database (with no data). This database has the schema
changes.
C. Then connect to the customer's database, which has the
original schema and the customer's data.
D. Make sure that the "active" database is the developer's (revised)
database. Go into the dictionary. In the lower left-hand corner
of your screen is the word "Database:", and next to it is the
name of the database that is "active". If it is not the developer's
database, choose the "DATABASE" option from the Dictionary Menu.
Then choose "S. Select a Working Database". A list appears that
shows all the connected databases. Choose the developer's
database.
E. Choose the "DATABASE" option off the Dictionary Menu. Choose the option:
"P. PROGRESS Utilities". From this sub-menu, choose the option:
"I. Create Incremental .df File".
F. A list of the other databases that are connected appears.
Choose the customer's database.
G. After choosing the database to compare, a prompt appears for the
name for the "changes" file. The default name for this file is
"delta.df".
H. After you choose the output name and press RETURN, two
boxes appear at the bottom of your screen. The left box is
the "SCANNING" box. It will scan the developer's database
(the one that is "active"). The right box is the "WORKING"
box. It scans the customer's database (or the database you chose
in step F) for differences.
I. When the test is done, apply the changes to the customer's
database after disconecting from the developer's
database, or exit the dictionary and apply the changes later.
To Apply the Changes:
---------------------
A. In the Data Dictionary, choose the ADMIN option on the Main Menu.
B. From the Admin menu, choose the option: "L. Load Data and
Definitions".
C. From the next menu, choose the option: "D. Data Defintions (.df file)".
file)".
D. You see the following: "Read input from file:" and a filename
with the .df extension. Change this name to the name of the
"changes" file you chose in step G above (delta.df), and press the
<GO> or CTRL-X) key.
E. You see the changes loaded into the customers database.
F. You will need to recompile your programs that contain references
to the files that have been changed by this procedure.
Loading an incremental .df file changes the database timestamp.
G. The incremental dump/load is complete.
OTHER NOTES:
============
1. Any flavor of PROGRESS may load in data definitions including the
incremental data definitions. If you have RUNTIME PROGRESS, you
will need to use the -rx option to get to the editor, where you
can type "dict" and hit F1 to get into the dictionary.
2. All data definitions are stored in the same format. Therefore,
transferring from one platform (i.e. DOS) to a different platform
(i.e. VMS) is no problem and there are no extra steps involved.
REFERENCES TO WRITTEN DOCUMENTATION:
====================================
PROGRESS System Administration II: General Guide, Chapter 4, Pg 4-59.
PROGRESS Developer's Toolkit, Chapter 9, Pg 9-3.
Progress Software Technical Support Note # 155