Post reply

Table locks resulting from trigger

  • November 12, 2007 at 5:52 pm

    #750425

    That's the entire trigger. Also, sorry about the confusion. I didn't understand what was missing in my replies.

    It is the ACCPAC ERP software that provides an interface to the OEORDH table. And since I have not developed it, I don't have access to the SQL code they use to insert data into the table. I hope this doesn't mean we have reached a dead end.

  • November 13, 2007 at 12:51 am

    #750501

    You can use profiler to capture the insert statements, and also to check is the app is doing a begin transaction before the insert and when/if it is doing the commit.

    Gail Shaw
    Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
    SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

    We walk in the dark places no others will enter
    We stand on the bridge and no one may pass

  • November 13, 2007 at 5:55 am

    #750620

    Karim,

    a lot depends on the way how data is inserted. Please follow Gila's suggestion and run Profiler trace to find out what happens on database level when the software inserts into OEORDH table.

    Some software has a strange way of inserting - for example, it inserts partially blank row and then updates it immediately. To find out where the problems come from we need to know what is happening.

Viewing 3 posts - 16 through 17 (of 17 total)

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