August 11, 2010 at 3:24 am
I have a very odd behaviour in our environments (dev, test and prod).
One package, quite predictably, fails when trying to convert a string ('KM') to an int.
But then the next package to run slows down from a normal 1-5 min to 2-10 hours.
The packages shares the same databases, but have no tables in common and there are no relationsships between their tables.
When I've tried to reproduce the problem during daytime the second package runs in a normal time. I've used the same data, caused the same error, run them by the same user.
Generally I would think that this is coincidence, but it has happened 3 times in the last two weeks.
Anyone else seen behaviour like this?
August 11, 2010 at 3:41 am
I noticed that the packages have the same ID. I don't know if this is relevant though.
Also, when checking the performance log one can see that the virtual servers are neither using the hard drive nor the processor during the long (slow) execution.
August 11, 2010 at 7:56 am
I think it is best if packages do not have the same ID.
It could be related (or maybe not). Change the ID in one of the packages and see what happens...
Need an answer? No, you need a question
My blog at https://sqlkover.com.
MCSE Business Intelligence - Microsoft Data Platform MVP
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply