Hello,

I have a DTS package ("pkg1") on Server 1, and it's last task is an
Execute Package Task. The package it executes ("pkg2") is on Server
2. Where does the actual processing take place for pkg2?

My situation is such that pkg1 exports a text file, zips it up, then
transfers it across the network to Server 2. Then, as its last step,
it calls pkg2 on Server 2, which unzips the file and imports it to a
database on Server 2. The problem I'm noticing is that the zip task
on pkg1 completes relatively quickly, but the unzip task of pkg2 seems
to execute much slower. Considering these two servers are about 400
miles apart and our connectivity between the two offices is absolutely
lousy--I could burn the data to a disc and fly it down there faster
than a regular DTS data transfer--I'm suspecting that the processing
of pkg2 is actually taking place on pkg1. Please tell me I'm wrong.

I considered putting pkg2 on a schedule so that it's not being
triggered at all from Server 1, but that's just not feasible. When we
do these data transfers, its because we need the data ASAP.

By the way, I use BCP for exporting and importing within the
packages. It's the fastest way we can move millions of rows between
the two offices.

Thanks for any help,
Eric

Yes, Eric, it is working exactly as you suspect. The second package on
Server2 is running on Server1.

Create a job on Server2 and issue an sp_start_job from the Pkg1 on
Server1 utilizing an Execute SQL Task connected to Server2.

Norman Kelm
DTS Package Search
http://www.dtspackagesearch.com/

On Mar 7, 2:06 pm, Eric Bragas <ericbra... (AT) yahoo (DOT) com> wrote:

Yes, Eric, it is working exactly as you suspect. The second package on
Server2 is running on Server1.

Create a job on Server2 and issue an sp_start_job from the Pkg1 on
Server1 utilizing an Execute SQL Task connected to Server2.

Norman Kelm
DTS Package Search
http://www.dtspackagesearch.com/

On Mar 7, 2:06 pm, Eric Bragas <ericbra... (AT) yahoo (DOT) com> wrote:

Yes, Eric, it is working exactly as you suspect. The second package on
Server2 is running on Server1.

Create a job on Server2 and issue an sp_start_job from the Pkg1 on
Server1 utilizing an Execute SQL Task connected to Server2.

Norman Kelm
DTS Package Search
http://www.dtspackagesearch.com/

On Mar 7, 2:06 pm, Eric Bragas <ericbra... (AT) yahoo (DOT) com> wrote:

Yes, Eric, it is working exactly as you suspect. The second package on
Server2 is running on Server1.

Create a job on Server2 and issue an sp_start_job from the Pkg1 on
Server1 utilizing an Execute SQL Task connected to Server2.

Norman Kelm
DTS Package Search
http://www.dtspackagesearch.com/

On Mar 7, 2:06 pm, Eric Bragas <ericbra... (AT) yahoo (DOT) com> wrote:

Yes, Eric, it is working exactly as you suspect. The second package on
Server2 is running on Server1.

Create a job on Server2 and issue an sp_start_job from the Pkg1 on
Server1 utilizing an Execute SQL Task connected to Server2.

Norman Kelm
DTS Package Search
http://www.dtspackagesearch.com/

On Mar 7, 2:06 pm, Eric Bragas <ericbra... (AT) yahoo (DOT) com> wrote:

Yes, Eric, it is working exactly as you suspect. The second package on
Server2 is running on Server1.

Create a job on Server2 and issue an sp_start_job from the Pkg1 on
Server1 utilizing an Execute SQL Task connected to Server2.

Norman Kelm
DTS Package Search
http://www.dtspackagesearch.com/

On Mar 7, 2:06 pm, Eric Bragas <ericbra... (AT) yahoo (DOT) com> wrote:

Yes, Eric, it is working exactly as you suspect. The second package on
Server2 is running on Server1.

Create a job on Server2 and issue an sp_start_job from the Pkg1 on
Server1 utilizing an Execute SQL Task connected to Server2.

Norman Kelm
DTS Package Search
http://www.dtspackagesearch.com/

On Mar 7, 2:06 pm, Eric Bragas <ericbra... (AT) yahoo (DOT) com> wrote:

Yes, Eric, it is working exactly as you suspect. The second package on
Server2 is running on Server1.

Create a job on Server2 and issue an sp_start_job from the Pkg1 on
Server1 utilizing an Execute SQL Task connected to Server2.

Norman Kelm
DTS Package Search
http://www.dtspackagesearch.com/

On Mar 7, 2:06 pm, Eric Bragas <ericbra... (AT) yahoo (DOT) com> wrote:

Thank you very much, Norman. I can see wzunzip.exe and bcp.exe
running on Server1 in the Task Manager, so I was forced to find
another route. Since I knew a Job could handle that, I ended up doing
exactly as you suggested. Before I call the Job on Server2, however,
I find I must use an ActiveX script to update the pkg2 global
variables and then re-save the DTS package in order to get the proper
default values. Do you know if there's a better way, such as
modifying the Job before calling it?

Thanks,
Eric