JAMS SQL Server integration
SQL Server Job Scheduling Across Every Server
JAMS Scheduler runs SQL Server Agent jobs, stored procedures, and SQL commands from one place, with dependencies that cross servers and platforms. Keep your Agent jobs where they are, or move them when you’re ready.
Three SQL job types
SQLAgent, SQLStoredProc, and SQLCommand
Authentication
Integrated, SQL Server, or Azure authentication
Define once
Each server lives in the Connection Store and every job reuses it
What JAMS Scheduler Runs in SQL Server
Each SQL job points at a connection in the JAMS Connection Store, so the server and database are defined once. Schedules, dependencies, and alerts work like any other job.
How JAMS Scheduler Connects to SQL Server
A SQL Server connection holds the server, instance, and database. Its credential can be a domain service account for integrated security or a SQL Server login, and you can override it on a single job.
Each connection has its own security settings. Only accounts with Submit permission on it can run jobs against that server.
Requirements
JAMS database
SQL Server 2022, 2019, 2017, or 2016
SSISDirect jobs
SQL Server Client Tools SDK shared features (2019, 2017, or 2016)
Connection credential
Domain service account or SQL Server login
SQL Server Jobs in a Cross-Platform Workflow
A stored procedure on one server can wait for an Agent job on another, then trigger an SSRS report and an SAP job. All of it shows up in one job history.
Planning to retire SQL Server Agent altogether? The SQL Agent migration page covers moving existing jobs into JAMS Scheduler.
Case Study
UVA Health Cures SQL Agent Ailments with JAMS
Hosting critical applications and business processes on multiple platforms had created a variety of pressure points for UVA Health’s workload automation tools. Failures and delays caused by the shortcomings of these tools were unacceptable.
SQL FAQ
Can JAMS Scheduler run my existing SQL Agent jobs?
Yes. The SQLAgent execution method starts a SQL Server Agent job and tracks it as a JAMS job, so you can add dependencies and alerts without rebuilding it.
Do I have to replace SQL Server Agent?
No. You can run Agent jobs from JAMS Scheduler and leave them where they are. If you’d rather move them, the SQL Agent migration page covers it.
Which SQL Server versions does the JAMS database support?
SQL Server 2022, 2019, 2017, and 2016, including clustered and Availability Group setups. Azure SQL Managed Instance also works, with known performance limits.
