January 22, 2012 at 5:52 pm
Hi
Our DBA hasn't been able to uncover the reason behind this. We have an SSIS package in out SQL2005 server to load data onto our system every night. The SSIS package consists of several ETL's(around 20) that are currently run sequentially.
On some nights it spits out below deadlock messages for certain ETL's.
Some nights no errors at all. Every night what's run on the server is the same.
The specific ETL's deadlocking are not the same. ie: Monday it'll be ETL1, ETL3, ETL9
Tuesday & Wednesday all ok. Thursday ETL2, ETL5, ETL6, ETL7
Friday all ok
Below last night's message.
Pl help uncover this Mystery
------------------------------------------------------------
Started: 9:00:22 PM
Error: 2012-01-22 21:02:02.38
Code: 0xC002F210
Source: Overnight Load Execute SQL Task
Description: Executing the query "EXEC ETL.[Overnight Load]" failed with the following error: "Transaction (Process ID 70) was deadlocked on lock resources with another process and has been chosen as the deadlock victim. Rerun the transaction.". Possible failure reasons: Problems with the query, "ResultSet" property not set correctly, parameters not set correctly, or connection not established correctly.
Viewing 0 posts
You must be logged in to reply to this topic. Login to reply