Re: autocommit ON but no commits visible in v$sqlarea

To the database autocommit and committing after every statement is the same thing. (Oracle, the database, does NOT have an autocommit mode, the the driver or the client software is issuing a commit statement after each statement.) Probably should have clarified that.

By committing more often than you have to you potentially slow things down. A commit forces the log buffer to flush (even if it isn't full) and you have to wait for the write. So if all the connections are doing this then the log buffer is flushed to disk before it gets full and you are wasting buffer. Think of in C doing a flush on every character you write to a file. Not as fast as writing say 32k out at a time. Same basic concept.

Jim

<dev_at_null> wrote in message
news:em3n0v8fvmf6msp5vp34l73m3k0pv3qbqq_at_4ax.com...
> On Wed, 25 Dec 2002 13:44:39 GMT, "Jim Kennedy"
> <kennedy-down_with_spammers_at_attbi.com> wrote:
>
> > Try not using auto commit. The waits will probably go away if you do.
> > Autocommit is not a good idea.
> > Jim
>
> Could you expand on that for me.
>
> I'll take a guess that one good reason is that it is a pretty d'uh
approach to
> implementing business logic.
>
> Are there also good technical reasons to avoid this? ...as in; what's the
> difference between autocommit and issuing an explicit commit on every
statement?
>
> TIA
>
> Steve Roach
Received on Thu Dec 26 2002 - 21:02:10 CST