Hi,

Can anyone help me. I have a whole bunch of DTS's that I would like to execute using one scheduled DTS. All I need the DTS to do is execute each DTS and on completion execute the next one. If I run the DTS's individually they run fine and fast, but as soon as I execute them within the DTS package they take for ever to execute. At present I am using 5 which when run by themselves take about 5 minutes max each. When I run them within a DTS package it takes 5 hours each, not ideal at all. Please can anyone help.

The DTS's access and right to a database, update some cubes, read flat files and do two data dumps. This is done in each DTS.

Thanks in advance

WHen they are all run together do you see resource contention? It sounds as
though you may be getting locking on the resources. If you are using 2000
you can use the ExecutePackage task to fire each from one hub package. I
would make sure all my connections were set to close on completion in their
workflow properties. You can also call each package in a piece of VBScript.

--

----------------------------

Allan Mitchell MCSE,MCDBA, (Microsoft SQL Server MVP)
www.allisonmitchell.com - Expert SQL Server Consultancy.
www.SQLDTS.com - The site for all your DTS needs.
I support PASS - the definitive, global community
for SQL Server professionals - http://www.sqlpass.org


"rmw" <anonymous (AT) discussions (DOT) microsoft.com> wrote

DTS and on completion execute the next one. If I run the DTS's individually
they run fine and fast, but as soon as I execute them within the DTS package
they take for ever to execute. At present I am using 5 which when run by
themselves take about 5 minutes max each. When I run them within a DTS
package it takes 5 hours each, not ideal at all. Please can anyone help.

I am currently using the Execute Package Task. It seems to take a long time for the DTS to start firing up, a bit like a cold car engine, but once it has started everything is fine and works as normal. It is just to get it starting literally takes hours

Any help?