Re: HELP: Long (lasting) transactions?

Roy F. Swonger (swonger@kwalty.enet.dec.com) wrote: : In article <3makt8$sv@hustle.rahul.net>, billb@lore.kla.com (Bill Baloglu) writes: : |>We are designing a C++ application which will initially : |>run on ORACLE (and subsequently may run on Sybase and : |>Informix). In this application, there will be scenarios : |>under which a database transaction may be open for a few : |>days. : : : |>Is there anyone who may wish to caution us on : |>any potential problems that such long lasting : |>transcations would present. : In general, I'd think that such long transactions would present a problem for : recoverability in any database system. It's sort of like backing up your : system disks; if you only do it every few days, can you really afford to lose : a few days' worth of data? With transactions, if some catastrophe occurs three : days into a transaction, can you really afford to have those three days of : activity be completely lost? Just because a transaction is long-lasting does not mean it is intensive. If the three days of activity consisted of three singleton updates, then it could be perfectly acceptable to have to redo it. There is no reason why any other activity during those three days should need to be affected. -- graeme -- Disclaimer: The author's opinions are his own, and not necessarily those of Pyramid Technology Ltd. or Pyramid Technology Inc. --------------------------------------------------------------------------- -m------- Graeme Sargent Voice: +44 (0)252 373035 ---mmm----- Senior Database Consultant Fax : +44 (0)252 373135 -----mmmmm--- Pyramid Technology Ltd. Telex: Tell who??? -------mmmmmmm- Farnborough, Hants GU14 7PL Email: graeme@pyra.co.uk --------------------------------------------------------------------------- We have the technology. The tricky bit is learning how to use it.