Post reply

Open Transaction

  • September 29, 2017 at 5:30 am

    #333124

    Every so often I find that a simple SELECT / UPDATE / INSERT statement run by a developer from SSMS, is blocking other processes. 
    When I investigate this, the specific developer process is an OPEN Transaction. I have spoken to and looked at the developer's query and there is no BEGIN TRAN, so it is not a case of him not committing or rolling back his transaction.
    He also does not have AutoCommit disabled in SSMS.
    His queries are usually quite simple select of singular insert that completes on his side, but yet it remains as an OPEN TRAN

    Any ideas?

  • September 29, 2017 at 5:40 am

    #1961584

    Ask him to go to Tools -> Options -> Query Execution -> ANSI and untick SET IMPLICIT_TRANSACTIONS.

    John

  • September 29, 2017 at 5:46 am

    #1961585

    Hi

    I checked that - that is the autoCommit I was referring to... it aint ticked...

  • September 29, 2017 at 5:54 am

    #1961588

    If he unticked it recently, is he still using the same query window?  He needs to open a new one for the change to take effect.  If that doesn't work, has he restarted SSMS? 

    John

  • September 29, 2017 at 5:59 am

    #1961591

    Yes he has restarted SSMS quite a few times and it still happens.... The strange thing is that this does not happen with all his queries. It seems random

Viewing 5 posts - 1 through 4 (of 4 total)

You must be logged in to reply to this topic. Login to reply