Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
yosiasz
Master Smack Fu Yak Hacker
1635 Posts |
 Posted - 2009-02-10 : 14:30:10
|
| greetingsMy SSIS package croaked with deadlocked error. I believe this happened when I was querying the tables the SSIS package Inserts into (testing this and sniffing t with SQl Profiler). Now the tool I am creating the user will be hitting these databases hard. I do not want this error to fail the SSIS package. I want my SSIS package to continue despite a possible deadlock, I want it to haev priority since it runs every 15 minutes, I do not want the user's front end killing my SSIS process with this deadlock issue.How can make it so that it prioritizes the finishing of the SSIS package over the users' need to query the database?Thanks!!! |
|
|
saurabhsrivastava
Posting Yak Master
216 Posts |
Posted - 2009-02-11 : 12:42:44
|
| SQl Server handles the deadlock internally, when deadlock occurs it looks for weakest victim in chain and kill it. What you can do is change package property to continue on error. |
 |
|
|
yosiasz
Master Smack Fu Yak Hacker
1635 Posts |
Posted - 2009-02-11 : 13:25:07
|
| thanks for your response! I could that but the next tasks depend on the value the failing task produces. So I am opting just to let it fail as it runs every 15 minutes.Does that sounds a good approach?Thanks |
|
|
|
|
|
|
deadlocked issue