SQL Server Reporting Services monitors the status of jobs that are running on the report server. At regular intervals, the report server does a scan of in-progress jobs and writes the status information to the report server database or the service application databases for SharePoint mode. A job is in progress if any of the following processes are underway: query execution on a remote or local database server, report processing, and report rendering.
You can manage both user jobs and system jobs.
An individual user or subscription can initiate user jobs. This process includes:
Running a report on demand
Requesting a report history snapshot
Manually creating a report snapshot
Processing a standard subscription
The report server initiates system jobs. System jobs include scheduled report execution snapshots, scheduled report history snapshots, and data-driven subscriptions.
Report processing time and resource use vary considerably depending on the report, the query complexity, the amount of data, and the rendering format that is specified for the report. Reports that have simple queries against a local data source often complete in milliseconds and never require management or tuning. In contrast, a large report that is rendered in PDF or Excel might require significant processing time. The time depends on hardware resources, delivery options, and whether other processes are running concurrently. On a report server, most long-running processes are report rendering operations and processes that are waiting for query processing to conclude. Occasionally, you might need to cancel a report process if you want to take a computer offline, or stop a running job that is taking too long to complete.
The following processes can be canceled:
On-demand report processing.
Scheduled report processing.
Standard subscriptions owned by individual users.
Canceling a job only cancels the processes that are running on the report server. Sometimes the report server doesn't manage data processing that occurs on other computers. So, you must manually cancel query processes that are orphaned on other systems. Consider specifying query time-out values to automatically stop queries that are taking too long to execute. For more information, see Set time-out values for report and shared dataset processing (SSRS). For more information about temporarily pausing a report, see Disable or pause report and subscription processing.
Note
In rare circumstances, you may need to restart the server to cancel a process. For SharePoint mode, you may need to restart the application pool hosting the Reporting Services service application. For more information, see Start and stop the Report Server service.
You can use SQL Server Management Studio to view or cancel a job that is running on the report server. You must refresh the page to retrieve a list of jobs that are currently running or to get up-to-date job status from the report server database. When you connect to a report server in Management Studio, you can open a Jobs folder to view a list of reports that are currently processing on the report server computer. Status information for each job is displayed in the Job Properties page. You can view status information for all jobs by opening the Cancel Report Server Jobs dialog box.
You can use SQL Server Management Studio to view or cancel a job that is running on the report server. You must refresh the page to retrieve a list of jobs that are currently running or to get up-to-date job status from the report server database. When you connect to a report server in Management Studio, you can open a Jobs folder to view a list of reports that are currently processing on the report server computer. Status information for each job is displayed in the Job Properties page. You can view status information for all jobs by opening the Cancel Report Server Jobs dialog box.
You can't use Management Studio to list or cancel model generation, model processing, or data-driven subscriptions. Reporting a service doesn't provide a way to cancel model generation or processing. However, you can cancel data-driven subscriptions by using the instructions provided in this article.
Right-click the report and then select Cancel Jobs.
How to cancel a data-driven subscription
Open the RSReportServer.config file in a text editor.
Find IsNotificationService.
Set it to False.
Save the file.
In Report Manager, delete the data-driven subscription from the Subscriptions tab of the report or from My Subscriptions.
After you delete the subscription, in the RSReportServer.config file, find IsNotificationService and set it to True.
Save the file.
Configure frequency settings to retrieve job status
A running job is stored in the report server temporary database. You can modify configuration settings in the RSReportServer.config file to control how often the report server scans for in-progress jobs and the interval after which the status of a running job changes from new to running. The RunningRequestsDbCycle setting specifies how often the report server scans for running processes. By default, status information is recorded every 60 seconds. The RunningRequestsAge setting specifies the interval at which a job is transitioned from new to running.
View and cancel jobs (SharePoint mode)
Management of jobs in a SharePoint mode deployment is completed by using SharePoint Central Administration, for each Reporting Services service application.
Manage jobs in SharePoint mode
In SharePoint Central Administration, select Manage service applications.
Find and select the name of your Reporting Services service application to open the page to manage the application.
Select Manage Jobs
Select the Job Id to see the details of the job.
Or choose the box for your job and select Delete to cancel the job. Deleting the job doesn't delete the subscription.
Manage jobs programmatically
You can manage jobs programmatically or by using a script. For more information, see ListJobs, CancelJob.
By using batch jobs, you can avoid slowing down your computer or the server during typical working hours. You can run many tasks in finance and operations apps as part of batch jobs. For example, batch jobs can include tasks for printing reports, performing maintenance, or sending electronic documents.