Re: HELP: Long (lasting) transactions?

Bill, I think you are pushing the concept of the transaction beyond its limits: the things are supposed to be discrete quanta of work. The quantum being being measured in seconds (at most) not days. What are other users going to do while locked out of the relevent pages/record? Archiving your log files will be problematic too. A better approach is in your design: set flags, use journalling - but don't go down that path - no matter what your Oracle Salesman tells you. Regards, Pete Harris On 10 Apr 1995, Bill Baloglu 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 > 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. > > Thanks in advance > > --bill >