G
gus
Guest
> On Jan 14, 2016, at 11:59 AM, Peter Judge wrote: > > The rare times you'd want break up an ASSIGN is to when some of the fields are part of an index and you need to ensure that an index constraint isn't violated. well ... don't do that. if you do that, you make 1 database operation (i.e. a create) into a create followed by one or more updates. this will happen because index entries contain the rowid of the record. since a rowid is an encoding of the storage location assigned to record (or the first fragment thereof) the rowid cannot be determiend without first creating the record. i once worked with a customer that had /half/ of their database workload on a big single table and its indexes. for every record created in that table, there was a create followed by an update. when they fixed that, the volume of bi and ai data was reduced by roughly one fourth and the overall database workload was greatly lessened as well. performance was much better after.
Continue reading...
Continue reading...