May 5, 2009 at 2:14 pm
We've been running our DTS packages on SQL Server 2005 for almost a year now since migrating from SQL Server 2000. All of a sudden a few months back we started experiencing a strange bug that we can't explain. We've got a scheduled DTS package with a number of child packages that runs on a weekday basis. Every once in a while one of the child DTS packages stops running after an execute SQL task and moves on to the next child DTS package with no error. It's almost as if the workflow on success is being ignored and the package thinks it has completed successfully.
In the attachment I've uploaded, the execute SQL task is the one called Update forecast. Instead of moving on to the remove no-value SQL Task.
The worst part is that we have no idea when it's going to happen as it's a random thing.
Has anyone come across somthing similar to this?
Thanks,
Phil
May 7, 2009 at 7:26 am
Hey Phil,
Have you ever checked for deadlocks?
Tony
Things will work out. Get back up, change some parameters and recode.
May 7, 2009 at 8:15 am
I haven't thought of checking for that. Thanks for the tip. Is this a problem with DTS and sql 2005? We had some locking issues in the past before we migrated but it would never cause the package to abort prematurely like that.
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply