0

我偶尔会在 sql server 中遇到死锁。我创建了一个用于锁定非数据库操作(信用卡处理)的函数,因此不会发生重复。我的函数如下(对不起tcl,但是sql已经够清楚了)。谁能看到为什么偶尔会发生死锁????

proc ims_syn_lock_object { db object {timeout 30} {wait 1}}  {   
    if {[catch {
        while {true} {
            am_dbtransaction begin $db

            # read the object locks that aren't timed out       
            set result [am_db1cell $db "SELECT object from GranularLocks WITH (ROWLOCK,HOLDLOCK) where object = [ns_dbquotevalue $object] AND  timeActionMade > DATEADD(second,-timeout, GETDATE())"]

            # check to see if this object is locked and not timed out
            if { [string equal "" $result] } {
                break;
            } else {
                # another process has this object and it is not timed out. 
                # release the row lock
                am_dbtransaction rollback $db

                if { $wait } {
                    # sleep for between 400 and 800 miliseconds
                    sleep [expr [ns_rand 400] + 400]                    
                } else {
                    # we aren't waiting on locked resources.
                    return 0;
                }
            }            
        }

        # either the object lock has timed out, or the object isn't locked
        # create the object lock.          
        ns_db dml $db "DELETE FROM GranularLocks  WHERE object = [ns_dbquotevalue $object]"
        ns_db dml $db "INSERT INTO GranularLocks(object,timeout) VALUES ([ns_dbquotevalue $object],[ns_dbquotevalue $timeout int])"   

        # releases the row lock and commits the transaction
        am_dbtransaction commit $db    

    } errMsg]} {
        ns_log Notice "Could not lock $object. $errMsg"
        catch { 
            am_dbtransaction rollback $db 
        } errMsg
        return 0
    }
    return 1     

}


proc ims_syn_unlock_object {db object } {

    #simply remove the objects lock
    ns_db dml $db "DELETE FROM GranularLocks WHERE object = [ns_dbquotevalue $object]"

}
4

2 回答 2

1
  1. 尝试将 UPDLOCK 添加到第一个选择以强制排他锁

  2. 试试sp_getapplock为这种操作提供的。

个人更喜欢2号...

于 2009-10-26T21:08:31.723 回答
0

有死锁图会很有用。

SQL 死锁的发生不仅是因为涉及的查询,而且同样重要的是涉及的模式。例如,您可以通过完全有效和“正确”的查询获得读写器死锁,这仅仅是因为读写选择了不同的数据访问路径。如果在不涵盖“对象”列的 GranularLocks 上存在 timeActionMade 索引,我可以在您的情况下看到这种情况。但同样,解决方案将取决于实际的死锁是什么。

于 2009-10-26T21:08:23.050 回答