URGENT Stored Procedure Performance in a JOB versus DTS...

[SteveMe]

URGENT Stored Procedure Performance in a JOB versus DTS (Execute SQL Task) that is then called by a Job.

I was unable to find any documents pertaining to best practices for executing SP for night Jobs.

Is there any associated overhead when running DTS package that executes a stored procedure via an Ezecute SQL task versus just running a job that executes a stored procedure.

I really appreciate the time you took to either read this thread and/or respond. Thanks

 

[SQLDenis]

No, it should all be the same

Denis The SQL Menace
SQL blog:

http://sqlservercode.blogspot.com/

Personal Blog:

http://otherthingsnow.blogspot.com/

 

[mrdenny]

There will be a slight bit of overhead when running a DTS package. It shouldn't effect the query execution, just the amount of time it will take before the procedure starts to run.

When a dts package runs it starts DTSRUN.exe which then logs into the SQL Server and pulls down the info for the package which is then executed.

A job that runs the proc just runs the proc without having to launch much else if anything.

Denny
MCSA (2003) / MCDBA (SQL 2000)

--Anything is possible. All it takes is a little research. (Me)

http://www.mrdenny.com