Quick: superfluous update records

[Leonard_Berkowitz@harvardpilgrim.org]

HP3000; PowerHouse v. 8.19

Our major application uses Quick screens. Recently we have installed the Bridge
product (a subset or superset of Quest's Netbase) that creates transaction
logging files. Now that we have these files, we have spent some time analyzing
transactions.

One phenomenon that we have noticed is that there is a huge number of update
transactions. The before-image of the record is mostly spaces, with only the key
values present. The after-image, of course, is all of the data that the user
entered.

Quite a lot of I/O overhead, I would say.

The question is: Is this S.O.P. for Quick or is there something in the
application that if forcing incomplete records to be written to the data base
and then updated?
===================
Leonard S. Berkowitz
Perot Health Care Systems
(Harvard Pilgrim Health Care account)
voice: 617-509-1212
fax:   617-509-3737
pager: 781-226-2431