Running SQL SSIS Packages in JAMS

Follow

JAMS has the ability to run SQL SSIS packages through the SSIS Execution Method. This Execution Method uses dtexec.exe.

More information on this utility can be found here:
http://msdn.microsoft.com/en-us/library/ms162810.aspx?PHPSESSID=o1fb21liejulfgrptbmi9dec92

JAMS includes a Sample Job, DBMaintPlan, as an example: 


To execute an SSIS package saved to SQL Server using Windows Authentication, use the following source:

/SQL pkgOne /ser productionServer


To execute an SSIS package saved to the file system folder in the SSIS Package Store, use the following source:

/dts "\File System\MyPackage"

 

To validate a package that uses Windows Authentication and is saved in SQL Server without executing the package, use the following source:

 

 /sql pkgOne /ser productionServer /va

 

To execute an SSIS package that is saved in the file system, use the following code:

 

 /f "c:\pkgOne.dtsx" 

 

To execute an SSIS package that is saved in the file system, and specify logging options, use the following code:

 

 /f "c:\pkgOne.dtsx" /l "DTS.LogProviderTextFile;c:\log.txt"

 

Have more questions? Submit a request

Comments

  • Avatar
    Charlie Demsky

    How can you set an SSIS variable for a file system package?

  • Avatar
    Gennaro Piccolo

    Hello Charlie, any JAMS parameters set on an SSIS or SSISDirect job will be matched to package variables of the same names.

  • Avatar
    Rick Culpepper

    Actually, Gennaro, i think that there is a difference between SSIS and SSISDirect execution methods. If I am not mistaken, SSIS matches Job parameters only to package-level variables in the SSIS Package while SSIS Direct matches job parameters to either package-level or project-level variables. This is a very important difference if you use project-level variables.