JAMS SSRS integration
SSRS Report Scheduling and Automated Distribution
JAMS Scheduler runs SQL Server Reporting Services reports after the data behind them finishes loading, saves the output where you want it, and emails it out.
Execution method
SSRS, built in
Delivery
Saved to a file location, emailed over SMTP
Report picker
Lists every report on the server you can reach
What JAMS Scheduler Runs in SSRS
Point the job at your report server and pick the report from the list. Choose the format, where the copy goes, and its title. Schedules, dependencies, and alerts work like any other job.
How JAMS Scheduler Connects to SSRS
You give the job the report server address and an authentication method. Once the server is set, the report path drop-down fills with every report you can reach.
Run SSRS jobs on the server where the reports and SQL libraries live. The account the job runs as needs Log on as a batch job, plus access to the folder where reports are saved.
Requirements
Report server
SQL Server Reporting Services
Run as
A credential with Log on as a batch job
An SMTP mail server connection
Recommended host
The server with the reports and SQL libraries
SSRS Reports in a Cross-Platform Workflow
Make the SSRS job wait on the SSIS package or SQL Server job that loads its data, so it runs when the data is ready. Then send the file on with a file transfer.
If the load runs late, the report waits with it.
SSRS FAQ
Can JAMS Scheduler email an SSRS report?
Yes. The SSRS job saves the report, and the Send a report as an e-mail schedule item mails it. You need an SMTP server connection configured.
Where should SSRS jobs run?
On the server where the reports and SQL libraries live. That’s the setup the JAMS documentation recommends.
Can an SSRS report wait for its data load?
Yes. Give the SSRS job a dependency on the SSIS package or SQL job that loads the data, and it starts only after that job finishes.
