EXEC a DTS Package
-
I’m trying to create a shortcut on a user’s machine in order to fully execute a DTS package. Is there a simple way to do this so that the user can manual run the dts package from there desktop? I have in the past saved the DTS package as vb and then created an execute file, however I would like to see if there is way to not create the VB and just run the DTS.
-
A better option than providing a shortcut to execute the DTS package, would be to setup the pacakge as a scheduled job without a schedule. Then use sp_start_job to execute the job whenever you need the package run.
This will ensure the package runs on the server, not the users workstation. It will also avoid the numerous authentication issues that arise from a user executing a DTS package.
Hope this helps
Phill Carter
--------------------
Colt 45 - the original point and click interface
--------------------
Colt 45 - the original point and click interface
-
I would use Phil's suggestion though you can build a batch file that calls DTSRUN with a a parameter for the package. The package could be on either the server or a flat file (.dts)
Steve Jones
http://www.sqlservercentral.com/columnists/sjones
The Best of SQL Server Central.com 2002 - http://www.sqlservercentral.com/bestof/
-
quote:
A better option than providing a shortcut to execute the DTS package, would be to setup the pacakge as a scheduled job without a schedule. Then use sp_start_job to execute the job whenever you need the package run.This will ensure the package runs on the server, not the users workstation. It will also avoid the numerous authentication issues that arise from a user executing a DTS package.
Hope this helps
Phill Carter
--------------------
Colt 45 - the original point and click interface
But in order to run SP_Start_Job it has to run from QA, right? I want to be able to simply have the end user execute either DTS or Job as easy as possible. These users are not that savvy to have to run a backup using QA.
Edited by - kbrady on 10/02/2003 08:41:14 AM
-
No, you can run it from any sort of front-end the same you would any other stored procedure or SQL statement. You could set it up in a batch file, put in a VB application, or execute it from a web page.
I would also produce a stored procedure that the user executes which is a wrapper around sp_start_job. This procedure would check if the job exists, is already running, etc... and give some nice feedback to the user.
Hope this helps
Phill Carter
--------------------
Colt 45 - the original point and click interface
--------------------
Colt 45 - the original point and click interface
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply