Folks, (sorry bit of a long story)

I Tested a DTS package last week. Nothing too complicated one connection to
SQL DB and one to Oracle DB. It runs thirteen select and update statements
against the Oracle DB.

Last week I terminal served into the SQL server box the job is on and set it
going. The DTS package ran in approx two hours.

Migration was last night. The user connected from his PC to another server
and was running Enterprise Manager on that server which had a connection to
the server the DTS package was on.

Five hours into migration four of thirteen jobs completed and the plug had
to be pulled.
Using Spotlight we could see nothing happening on SQL server and an inactive
session on the Oracle connection. Every once in a while for two or three
seconds this would turn to active.

In SQL Server we were getting wait type = NETWORKIO wait time = 5563.

I suppose the simple question is was this caused by not terminal serving to
the server? I thought that if you are in EM on your PC but connected to the
server the job was run locally on the server. Or does it run locally on your
machine?

Any pointers / ideas / links welcome as I am a bit puzzled by the situation.

Thnaks In Advance,
MPM

If you start a job from EM on your workstation, the job will be run on the
server. If you open a DTS Package in EM on your workstation, the Package
will be executed on your workstation, not on the server. That could involve
pulling data from the server to your workstation, depending on what the DTS
package does.

--
Jacco Schalkwijk
SQL Server MVP


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