February 10, 2009 at 3:02 am
hi
i have a daily package that runs 15 packages in parallel (and one before and one after the 15)
it runs fine when i run it in BIDS, taking 40 minutes
when i run it on server, it runs one of the parallel tasks (i know this as i have a little log table) and then seems to hang for three hours (it could hang for more, but i kill it)
has anyone got anything i can try/test that would make a difference between running a package on BIDS and on the server
February 10, 2009 at 7:17 am
When you run it from BIDS, are you running against the same database? Your post wasn't clear if you are using a separate testing environment. If the deployment is going from a test environment to a production environment, you may have an issue with resource contention in production. Your package may be blocked by another process.
More information about monitoring blocking can be found at http://support.microsoft.com/kb/271509.
hth,
Tim
Tim Mitchell
TimMitchell.net | @tmitch.net | Tyleris.com
ETL Best Practices
February 10, 2009 at 7:32 am
hi Tim
thanks for that...but i suspect it isn't blocking as it's the same server from BIDS and deployment (although i'm by no means a blocking expert!)
i can't see anything in the system tables to suggest blocking either
annoyingly, everything looks to be working ok in series in a job, but the master package with all of them in parallel doesn't run so well
hmm
worse case scenarion i'll have lots of jobs running in parallel
February 10, 2009 at 7:41 am
OK, if I understand correctly, it runs fine when you run the packages serially (one after another) but it's not completing when they run in parallel. If that is the case, you've almost certainly got issues with resource contention and likely a lot of disk I/O.
hth,
Tim
Tim Mitchell
TimMitchell.net | @tmitch.net | Tyleris.com
ETL Best Practices
February 10, 2009 at 7:44 am
ah, ok
seems strange it would run ok in BIDS though
i'll chop it up and see what happens
many thanks
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply