Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase

Execute SSIS Package from SP or From Windows Application Expand / Collapse
Author
Message
Posted Tuesday, September 9, 2008 3:03 AM
Grasshopper

GrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopper

Group: General Forum Members
Last Login: Thursday, March 17, 2011 1:39 AM
Points: 14, Visits: 50
Hello,

How to Execute a SSIS Package from Stored Procedure? Or From Windows Application?


thanks in advance.
Vijayraj
Post #565979
Posted Tuesday, September 9, 2008 3:25 AM
Grasshopper

GrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopper

Group: General Forum Members
Last Login: Thursday, January 14, 2010 5:18 PM
Points: 12, Visits: 310
I think you can use dstrun.exe to execute the package. Since its an exe, u don't need to install it on client/destination pc.
Post #565989
Posted Tuesday, September 9, 2008 5:14 AM
SSCrazy

SSCrazySSCrazySSCrazySSCrazySSCrazySSCrazySSCrazySSCrazy

Group: General Forum Members
Last Login: Tuesday, August 10, 2010 5:07 AM
Points: 2,661, Visits: 23,078
An SSIS package can only be run on an SSIS Server of the appropriate Edition Level. Although you can author a package using BIDS on a machine with only the SQL Client tools installed, it will not run from the command line on that machine without SSIS installed. There is no included remote execution functionality for telling a package to run on the SSIS server from a client machine (other than the SQL Job agent, arguably). Running the package on a machine without the correct edition of SSIS installed gives a vague error message about insufficient product level.

An SSIS package can be executed from within an application using the DTExec command line or through the SSIS object model, but you must be on an SSIS server. So, if you intend to distribute an application that runs SSIS packages locally on a workstation, be prepared to purchase and install a SQL Server license on every client machine.

It is pretty easy to build a web service that will run an SSIS package on the server. It can then be called from a client machine and only require a SQL CAL rather than a full SSIS install on each machine.
Post #566039
Posted Tuesday, September 9, 2008 5:44 AM
Grasshopper

GrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopper

Group: General Forum Members
Last Login: Thursday, March 17, 2011 1:39 AM
Points: 14, Visits: 50
Thanks for the reply.
i m succeded with DTExec command.
But not aware of how to use SSIS object model.
Post #566053
Posted Tuesday, September 9, 2008 5:28 PM
SSC-Enthusiastic

SSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-Enthusiastic

Group: General Forum Members
Last Login: Wednesday, November 17, 2010 5:56 PM
Points: 185, Visits: 637
Running a package from .NET code can be found here:
http://msdn.microsoft.com/en-us/library/aa337077.aspx
Post #566537
Posted Wednesday, November 30, 2011 10:23 AM
Grasshopper

GrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopper

Group: General Forum Members
Last Login: Wednesday, September 24, 2014 4:10 AM
Points: 24, Visits: 120
I found that it stopped working with the following sql statement
"Select col1,col2 from table1 where (col1 = " + @[User::IDMEDIUM] +")"

M.L.
Post #1214116
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse