Results 1 to 4 of 4

Thread: deadlocked on thread | communication buffer

  1. #1
    Join Date
    Sep 2002
    Posts
    159

    deadlocked on thread | communication buffer

    Sql version
    Microsoft SQL Server 2000 - 8.00.818 (Intel X86)
    May 31 2003 16:08:15
    Copyright (c) 1988-2003 Microsoft Corporation
    Standard Edition on Windows NT 5.0 (Build 2195: Service Pack 4)

    I have dts running 24 X 7 every 5 minutes
    I noticed DTS failed few times a day with error

    Step Error Source: Microsoft OLE DB Provider for SQL Server
    Step Error Description:Transaction (Process ID 74) was deadlocked on thread | communication buffer resources with another process and has been chosen as the deadlock victim. Rerun the transaction.
    Step Error code: 80004005
    Step Error Help File:
    Step Error Help Context ID:0

    The is no entry about in Server server log files.
    will trace identify deadlock and why deadlock info not entred into log file ?

  2. #2
    Join Date
    Nov 2002
    Location
    New Jersey, USA
    Posts
    3,922
    Start trace in the SQL Server to identify tables or indexes involved in deadlock. Trace will also tell you what was other process doing at that time

    dbcc traceon (-1,3605)
    dbcc traceon (-1,1204)

  3. #3
    Join Date
    Sep 2002
    Posts
    159
    thank a lot , it work just fine.I captured deadlock
    if l traces continue to run will affect performance ?

  4. #4
    Join Date
    Sep 2002
    Posts
    5,938
    Yes, but not much.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •