Re: Problem with Update

This kind of behavior is normally caused by one or more of the following (relief action suggested) in order of increasing correction cost: - Table statistical distributions are outdated - Run the recommended suite of update statistics commands per the Performance Guide- Index(es) have become inefficient due to repeated key field updates or row deletes and inserts - Drop and recreate all indexes especially those on columns that are commonly updated, then rerun stats as above. - Table has become fragmented, too many extents - Reorganize the table to consolidate. The stats update can be automated. There are several scripts and my dostats utility which implement the recommended suite of commands with various levels of options and features. Dostats is the most feature rich and is part of the package utils2_ak which is available for download from the IIUG Software Repository. Art S. Kagel ----- Original Message ----- From: Mohamed.Afe.... <mohamed.afeilal@meditel.ma> At: 3/17 20:59 > Hello everybody > > We noticed these last days a probleme at the time of the execution of the > update commande. The commande make 2 hours and half to be executed, whereas > it did not exceed a half front hour. > The request updates 50 thousand recordings in only one transaction. > When we carried out the some command under dbaccess, we pointed out that > the update of the first 10 thousand are done in a second and that for the > remainder the request becomes increasingly slow. > > We put the following questions : > > - Our current configuration does not allow an update of 50 thousand > recordings > - It's necessary to commit at the end of each 10 thousand recordings > - There are parameters to modify to support an update of 50 thousand > recordings in one transaction > > The situation becomes very critical and I count on your assistance . > > Best Regards > M. AFEILAL