|
Home > Archive > MS SQL Server > July 2005 > DTS and Client Routing
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
DTS and Client Routing
|
|
|
| Our shop executes "on the fly" DTS packages that copy (with a few
transformations, etc.) from one database to another database all on the same
server. One of the problems we have is that DTS routes the data stream
through the client which gives quite slow response time even for simple DTS
packages. Is there any way around this?
Surely, there's got to be a way to keep the data stream on the server
itself. All help is appreciated.
| |
| Narayana Vyas Kondreddi 2005-07-27, 8:23 pm |
| Run the package as a job on the server. That's the simplest way to achieve
this. Also, you could terminal service onto the server and then invoke the
DTS package from the server itself, instead of running it from a client
machine.
--
HTH,
Vyas, MVP (SQL Server)
SQL Server Articles and Code Samples @ http://vyaskn.tripod.com/
"CLM" <CLM@discussions.microsoft.com> wrote in message
news:F98323F3-1D6A-4819-B160- 376A37C024DA@microso
ft.com...
> Our shop executes "on the fly" DTS packages that copy (with a few
> transformations, etc.) from one database to another database all on the
> same
> server. One of the problems we have is that DTS routes the data stream
> through the client which gives quite slow response time even for simple
> DTS
> packages. Is there any way around this?
>
> Surely, there's got to be a way to keep the data stream on the server
> itself. All help is appreciated.
|
|
|
|
|