DTS or stored procedure

I need to copy some rows from a table in one server to a table in another
server. The amount of data is not very large and nothing fancy happens to
the data on the way.
Does anyone have any advice on the reletive merits of DTS as opposed to just
doing it in a stored procedure?
regards
SpikeHi
In your situation there is probably very little difference. You are not
really using any of the more specialised features of dts!
If you don't have any other DTS packages then there would be no real reason
to create one just for this.
John
"Spike" wrote:

> I need to copy some rows from a table in one server to a table in another
> server. The amount of data is not very large and nothing fancy happens to
> the data on the way.
> Does anyone have any advice on the reletive merits of DTS as opposed to ju
st
> doing it in a stored procedure?
> regards
> Spike
>|||Spike,
One should use DTS only if it is entirely necessary. For all other situation
one shd code the same thing using a sproc. Specifically in your case where
nothing fancing is happening to your data on the way you are better off usin
g
a sproc.
There can be hundreds of difference between DTS and sproc.
just to start with: sproc can be faster than DTS (when properly coded).
although it can be a complex codingbut then hey thats why we get good money
for doing it isnt it ?
sproc are in your db itself and are backed up by your regular db backup.
nothing special needs to be done.
I believe for DTS if you back up your msDB then its okay. additionally DTS
can also be saved as a file. (but still its an extra effort)
DTS is nice to look at and fancy to work wiht coz you can use your vb script
skills and stuff.
Abhishek Pandey
"Spike" wrote:

> I need to copy some rows from a table in one server to a table in another
> server. The amount of data is not very large and nothing fancy happens to
> the data on the way.
> Does anyone have any advice on the reletive merits of DTS as opposed to ju
st
> doing it in a stored procedure?
> regards
> Spike
>