May 16, 2013 at 3:31 am
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.
May 16, 2013 at 3:37 am
What is 'CRM destination'? Is this a custom component?
The absence of evidence is not evidence of absence
- Martin Rees
The absence of consumable DDL, sample data and desired results is, however, evidence of the absence of my response
- Phil Parkin
May 16, 2013 at 4:17 am
Its a Third party component [Kingsway]
CRM DESTINATION ADAPTER [inserts data into Microsft CRM Dynamics]
May 16, 2013 at 4:28 am
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.
The absence of evidence is not evidence of absence
- Martin Rees
The absence of consumable DDL, sample data and desired results is, however, evidence of the absence of my response
- Phil Parkin
May 16, 2013 at 5:56 am
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 .
May 17, 2013 at 11:34 am
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.
May 20, 2013 at 1:57 am
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
May 20, 2013 at 2:15 am
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.
The absence of evidence is not evidence of absence
- Martin Rees
The absence of consumable DDL, sample data and desired results is, however, evidence of the absence of my response
- Phil Parkin
May 20, 2013 at 9:37 am
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 suggestYou 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