Is there a performance difference between running a DTS package from a
VBScript using DTSrun.exe opposed to directly executing the stored procedure
within QA. I would assume that one the VBScript throws the request over the
fence its all the same.
Also, I am using a an OLE DB Connection within the DTS package for my
connections and the sp I guess uses something else internally. Could that
affect the performance in comparison to a QA execution?

KC

In message <eE6xGW0xEHA.392 (AT) TK2MSFTNGP12 (DOT) phx.gbl>, Kevin C
<kc (AT) noneya (DOT) com> writes
hit running an sp from a DTS task as opposed to running the same sp from
QA, then no the proc should run the same. There will be some (time)
overhead in loading the package, executing the package and calling the
proc. The proc will take the same time, but loading DTS may take longer,
so that baggage may mean it is slower to the end user. Make sense?

Having a heavy wrapper like DTS just to run a proc does not make sense
if that is all that you do in the package. Use a simpler method such as
ADO(.Net) for example. Not really sure what you are doing of course, so
perhaps you can clarify is this doesn't make sense.


--
Darren Green (SQL Server MVP)
DTS - http://www.sqldts.com

PASS - the definitive, global community for SQL Server professionals
http://www.sqlpass.org