• Amit Pandey DeBugSQL (10/6/2010)


    Nope Snapshot is not turned on and turning it is not an available option (I have already recommended this).

    Yes I ran the query given by you and it gives me as many as 37 records.

    Please let me know if you need any further info.

    One of these queries is your likely culprit, then, in the actual deadlock cause. Deadlocks in general (it seems you're relatively aware, but to make sure) are caused by two transactions fighting over the same resources. If you don't have multi-statement transactions, it's nearly impossible to get a deadlock. Timeouts waiting for lock, sure... but not deadlocks.

    Look over your deadlock statistics again and check to see if one of those 37 are listed.


    - Craig Farrell

    Never stop learning, even if it hurts. Ego bruises are practically mandatory as you learn unless you've never risked enough to make a mistake.

    For better assistance in answering your questions[/url] | Forum Netiquette
    For index/tuning help, follow these directions.[/url] |Tally Tables[/url]

    Twitter: @AnyWayDBA