RE: Thoughts on implicit/auto COMMITs

From: Jeff Smith <>
Date: Thu, 15 Mar 2018 12:34:16 +0000 (UTC)
Message-ID: <b6b63970-c055-4dce-a202-d1f45dcf2547_at_default>

Brent is a friend and an ex-coworker. He wanted to share the background of this customer’s scenario, in case it would help you with yours.


I let Brent know some folks were…with his take on autocommit.





Heh heh heh, I can only imagine. The difference on optimistic vs pessimistic concurrency nailed it though - the default combo of optimistic & implicit transactions makes sense in Oracle, and the default of pessimistic and automatic transactions makes sense in SQL Server. It's when you change only one of those two settings that you're screwed.


The blog post stemmed from an app that had been written by SQL Server people, and then an Oracle guy came in and made a few changes. He switched to implicit transactions without understanding that everybody was doing single-line inserts/updates all over the place in code, not bothering to set transactions. He didn't understand the impact of what he was doing. (Not an Oracle jab by any means - the guy was well-meaning but just not prepared.)


We got called in because performance went straight into the toilet. Even worse, rollbacks were rolling back completely unrelated transactions, and nobody knew why, hahaha.



From: Noveljic Nenad <> Sent: Thursday, March 15, 2018 7:54 AM
To:; Cc:
Subject: RE: Thoughts on implicit/auto COMMITs


The setting is called the read_committed_snapshot which is set to off by default. This means that readers are blocking writers. Some applications might even rely on this behavior.


After setting read_committed_snapshot to on SQL Server will start to behave like Oracle in this respect. Row versions will be stored in the tempdb in such case.







From: HYPERLINK "" [] On Behalf Of Andy Sayer Sent: Donnerstag, 15. März 2018 12:19
To: HYPERLINK "" Cc: HYPERLINK "" Subject: Re: Thoughts on implicit/auto COMMITs


In ye olde regions of SQL Server land, writers block readers. This has spawned many silly workarounds like

Commit constantly

If a transaction is open for more than a second it must be killed


I believe there is some setting in more recent versions to prevent this. The workarounds are so blindly followed as best practise that the greener grass is a mystery to some.


Obviously this just doesn’t apply in the sane land of Oracle, writers don’t block readers. 





On Thu, 15 Mar 2018 at 09:13, Arian Stijf <HYPERLINK ""> wrote:


in my opinion this breaks the A(tomicity) of ACID. E.g. a transaction consisting of two dependent inserts (Parent/child), and the first insert is commited before the second, then the database crashes.



On 14-Mar-18 16:57, Rich J wrote:
> Hey all,
> As a solo DBA responsible for a number of SQL Servers in addition to
> Oracle, I try to read up on both.  One of the (more respected) SQL
> Server team blogs had this entry:
> ..where they advocate the default auto-commit because otherwise the
> row (or page, or table) is locked should someone forget to COMMIT.
> This seems like an extraordinarily bad idea for anything but ad-hoc or
> one-off DML (without getting into a sidebar on that particular
> practice), whether Oracle or SQL Server or whatever.
> Or is it just me and some old-fashioned narrow RDBMS thinking?
> Rich



Please consider the environment before printing this e-mail.

Bitte denken Sie an die Umwelt, bevor Sie dieses E-Mail drucken.

Important Notice 
This message is intended only for the individual named. It may contain confidential or privileged information. If you are not the named addressee you should in particular not disseminate, distribute, modify or copy this e-mail. Please notify the sender immediately by e-mail, if you have received this message by mistake and delete it from your system. 
E-mail transmission may not be secure or error-free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete. Also processing of incoming e-mails cannot be guaranteed. All liability of the Vontobel Group and its affiliates for any damages resulting from e-mail use is excluded. You are advised that urgent and time sensitive messages should not be sent by e-mail and if verification is required please request a printed version.

Received on Thu Mar 15 2018 - 13:34:16 CET

Original text of this message