SQL Server import speeds

[Ralph Noble]

I have two avenues to access my primary SQL Server. (I work remotely
using a VPN connection.)

Usually, I hit the server from my local machine but I also login to a
desktop machine inside the main building using a terminal ap and hit
the server from that desktop.

Anyway, when I import files locally using the Enterprise Manager's DTS
import wizard, the process is incredibly slow. It doesn't matter if
the file is stored on my local machine or if the file is stored on the
same server that has SQL Server mounted.

It's as if the data from the file is being channeled to my local
machine and then back to the server. Shouldn't the entire process run
server-side?

When I use the EM import wizard through the terminal app, on the
desktop inside the building, the import process flies.

The only difference between the two setups is that I must add the
domain name to the address of the SQL Server and the same internal
server where the files are stored.

Can I do anything about this?

Thanks!

[Simon Hayes]

"Ralph Noble" <ra*********@hotmail.com> wrote in message
news:ed**************************@posting.google.c om...

I have two avenues to access my primary SQL Server. (I work remotely
using a VPN connection.)

Usually, I hit the server from my local machine but I also login to a
desktop machine inside the main building using a terminal ap and hit
the server from that desktop.

Anyway, when I import files locally using the Enterprise Manager's DTS
import wizard, the process is incredibly slow. It doesn't matter if
the file is stored on my local machine or if the file is stored on the
same server that has SQL Server mounted.

It's as if the data from the file is being channeled to my local
machine and then back to the server. Shouldn't the entire process run
server-side?

When I use the EM import wizard through the terminal app, on the
desktop inside the building, the import process flies.

The only difference between the two setups is that I must add the
domain name to the address of the SQL Server and the same internal
server where the files are stored.

Can I do anything about this?

Thanks!

The Import/Export wizard uses DTS, which is a client application, so you are
correct that it's pulling data to your workstation and then to the server.
If you need to run it server-side then you could save the package, schedule
it and start the scheduled job.

There's lots of good information on scheduling and executing DTS packages
here:

http://www.sqldts.com

Simon