Re: HELP: Long (lasting) transactions?

Bill Baloglu (billb@lore.kla.com) wrote: : 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. : We are told that under ORACLE, having a transaction open : for long durations (as in days) does not present any : significant impact on performance and other database : resources. Is this correct? What about with Sybase and It sounds dubious. It would depend on what kind of transactions, and how many of them. You should look at the impact on Rollback Segments and on recovery times. : Informix? Is there anyone who may wish to caution us on : any potential problems that such long lasting : transcations would present. I for one, thought that : there could be problems with tranaction log files. It's a bad way to design an application if you want portability. Even if you use it in such a way that it does not impact Oracle, there are bound to be implications for other database applications (eg the amount of disk you need for Logical Logs with Informix-OnLine). My advice would be: Think again. -- 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.