I'm familiar with the difference between a logical and physical transaction. I brought this up because it appears that people 'benchmark' large systems by the number of transactions they do. This appears to be a flawed method since a transaction in one system may be 1 action and a transaction in another could be many.
> I don't consider a transaction to be a technology thing but a logical
> concept relating to the application. It should be defined something
> like 'a logical grouping of work tasks that must all be performed
> together and should all succeed or all fail'.
>
> I see the classic banking example has already been given. Let me give another.
>
> We run invoices monthly. The process that does this creates updates
> and deletes a lot of data in an Oracle database (well we *hope* its a
> lot of data anyway) and then prints some crystal reports on headed
> paper, and for some customers I believe, now generated pdfs that get
> emailed out. The *transaction* in this case as covering all the data
> manipulation, plus the generation and sending of the printouts (if
--
http://www.freelists.org/webpage/oracle-l
Received on Wed May 04 2005 - 13:21:25 CDT
