Good points. Also I believe the default in the sql query tool is
autocommit.
Jim
"Kendall" <kendallwillets_at_yahoooo.com> wrote in message
news:pan.2001.12.31.10.31.05.466.8939_at_yahoooo.com...
> In article <5KZX7.36613$Q66.129567_at_NewsReader>, "Garrick Bigwood"
> <garrickb_at_software360.com> wrote:
>
> > Hello,
> >
> Looking at the trace files one of the problems with
> > Oracle seems to be the amount of physical writes done to datafiles and
> > rollback files(also redo of course), when I look at the SQL Server trace
> > files there does'nt to be any writing done.
>
> Just to clarify, are you doing a COMMIT after each update? I don't know
> exactly how SQL server handles these, but you may be right about delayed
> i/o. A commit should generate some kind of write to disk.
>
> Oracle only requires a write to the redo log on commit; any writes to
> datafiles are from cache flushing, or a checkpoint. If your SGA is too
> small you're obviously going to see more I/O. Check the SGA and SQL
> Server's cache size - they should be the same size for a fair test.
>
> Also, how many indexes are on the table/column? Is the column NULL before
> update?
Received on Tue Jan 01 2002 - 12:49:15 CST
