JAMS SSIS integration
SSIS Package Scheduling and ETL Orchestration
JAMS Scheduler runs SQL Server Integration Services packages after upstream loads finish and before downstream reports start, with alerts and logs in one place.
Two job types
SSIS and SSISDirect
Stored connections
SSISDirect uses a SQL Server connection from the Connection Store
In the chain
Packages wait on loads and feed reports
What JAMS Scheduler Runs in SSIS
Pick the package, set the connection and credential, and the package runs as a JAMS job. Schedules, dependencies, and alerts work like any other job.
How JAMS Scheduler Connects to SSIS
SSISDirect jobs point at a SQL Server connection in the JAMS Connection Store, so the server and database are defined once and reused.
To create, edit, or run SSISDirect jobs, the SQL Server Client Tools SDK shared features need to be installed on the machine running the JAMS Client and on the machine where the job runs.
Requirements
SSISDirect jobs
SQL Server Client Tools SDK shared features, 2019, 2017, or 2016
Where
The JAMS Client machine and the machine running the job
Connection
A SQL Server connection in the Connection Store
SSIS Packages in a Cross-Platform Workflow
A typical chain: a file transfer lands the source file, the SSIS package loads it, and an SSRS report goes out when the load finishes.
Moving SSIS jobs out of SQL Server Agent? The SQL Agent migration page covers it.
SSIS FAQ
What’s the difference between SSIS and SSISDirect?
Both run SQL Server Integration Services packages. SSISDirect uses a SQL Server connection from the JAMS Connection Store.
What does SSISDirect need installed?
The SQL Server Client Tools SDK shared features (2019, 2017, or 2016) on the machine running the JAMS Client and on the machine where the job runs.
Can an SSIS package wait for a file to arrive?
Yes. Give it a dependency on the file transfer job, or start it with a file trigger, and it runs once the file is there.
