Dead Lock Issue -In update Scenario

  • HI ,

    I have a Dataflowtask in which following following Transformations are used

    ---OLEDB Source[Pulls Data From X StagingTable]

    ---Balance data distributor is used [For Parallel Execution]

    ---CRM Destination is used for Inserts/Updates data into Y Target Table

    ---Conditional Split[On >0] exists.

    Case 1 [>0-Error]:Updates Table X's Row as Unsuccesful

    Case 2[<=0-No Error]:Updates Table X's Row as Succesful

    While Peforming above scenario Iam getting Dead Lock issue .

    "Microsoft SQL Server Native Client 10.0"

    Hresult: 0x80004005 Description: "Transaction (Process ID 82) was deadlocked on

    lock resources with another process and has been chosen as the deadlock victim. Rerun the transaction.".

    I belive this is due to Update operation performed on table

    Kindly request you to help me in this regard.

  • What is 'CRM destination'? Is this a custom component?

    If you haven't even tried to resolve your issue, please don't expect the hard-working volunteers here to waste their time providing links to answers which you could easily have found yourself.

  • Its a Third party component [Kingsway]

    CRM DESTINATION ADAPTER [inserts data into Microsft CRM Dynamics]

  • greeshatu (5/16/2013)


    Its a Third party component [Kingsway]

    CRM DESTINATION ADAPTER [inserts data into Microsft CRM Dynamics]

    If that's where the deadlocks are happening, can you ask them for support?

    It would be difficult for most people here to help you, given that this is not a standard component.

    If you haven't even tried to resolve your issue, please don't expect the hard-working volunteers here to waste their time providing links to answers which you could easily have found yourself.

  • Dead lock is not happening in Third part object CRM Destination adapter

    .Dead lock is Occuring in OLEDB Commmand's defined after Conditional Split where in Update Query on Staging table is coded .

  • greeshatu (5/16/2013)


    HI ,

    I have a Dataflowtask in which following following Transformations are used

    ---OLEDB Source[Pulls Data From X StagingTable]

    ---Balance data distributor is used [For Parallel Execution]

    ---CRM Destination is used for Inserts/Updates data into Y Target Table

    ---Conditional Split[On >0] exists.

    Case 1 [>0-Error]:Updates Table X's Row as Unsuccesful

    Case 2[<=0-No Error]:Updates Table X's Row as Succesful

    While Peforming above scenario Iam getting Dead Lock issue .

    "Microsoft SQL Server Native Client 10.0"

    Hresult: 0x80004005 Description: "Transaction (Process ID 82) was deadlocked on

    lock resources with another process and has been chosen as the deadlock victim. Rerun the transaction.".

    I belive this is due to Update operation performed on table

    Kindly request you to help me in this regard.

    Please see the parts I bolded in your explanation. Table X is the source. Is Table X also being updated? If YES, has the SELECT from Table X completed before said UPDATE? If not you may want to add an asynchronous component before your update to ensure the SELECT from X has completed before Updating X.

  • Select and Update are running paralelly .. this is because I have used Balance data distributor to run the tasks parallely .Which asyncronous transformations is helpful in this case.kindly suggest

  • greeshatu (5/20/2013)


    Select and Update are running paralelly .. this is because I have used Balance data distributor to run the tasks parallely .Which asyncronous transformations is helpful in this case.kindly suggest

    You might be better off selecting to a Raw file and updating from that - to ensure that you avoid contention issues.

    If you haven't even tried to resolve your issue, please don't expect the hard-working volunteers here to waste their time providing links to answers which you could easily have found yourself.

  • Phil Parkin (5/20/2013)


    greeshatu (5/20/2013)


    Select and Update are running paralelly .. this is because I have used Balance data distributor to run the tasks parallely .Which asyncronous transformations is helpful in this case.kindly suggest

    You might be better off selecting to a Raw file and updating from that - to ensure that you avoid contention issues.

    Raw file is a great idea Phil! Probably better than an asynchronous component in most cases. That said, if your'e only dealing with a smaller data set, add a Sort component. It should not add too much time to the overall processing and should do the trick as well.

    But I do like the Raw file very much!

Viewing 9 posts - 1 through 8 (of 8 total)

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