Export (0) Print
Expand All

Creating, Modifying, and Deleting Schedules

Use this topic to learn about how to create, modify, and delete schedules. You can use Report Manager or SQL Server Management Studio to work with shared schedules. If you are scheduling report and subscription processing on individual reports, you must use Report Manager.

NoteNote

If you configured a report server to run in SharePoint integrated mode, you can create and manage shared schedules from a SharePoint site. For more information, see How to: Create and Manage Shared Schedules (Reporting Services in SharePoint Integrated Mode).

Reporting Services uses SQL Server Agent as a timer for scheduled operations. SQL Server Agent must be running if you want to create a scheduled operation. The report server must also be configured to support scheduling and delivery operations. You can enable scheduling and delivery by setting the ScheduleEventsAndReportDeliveryEnabled property to True in the Surface Area Configuration for Reporting Services facet of SQL Server Policy-Based Management.

How you work with a schedule depends on tasks that are part of your role assignment. If you are using predefined roles, users who are Content Managers and System Administrators can create and manage any schedule. If you use custom role assignments, the role assignment must include tasks that support scheduled operations.

To do this

Include this task

Predefined roles

Create, modify, or delete shared schedules

Manage shared schedules

System Administrator

Select shared schedules

View shared schedules

System User

Create, modify, or delete report-specific schedules in a user-defined subscription

Manage individual subscriptions

Browser, Report Builder, My Reports, Content Manager

Create, modify, or delete report-specific schedules for all other scheduled operations

Manage report history, manage all subscriptions, manage reports

Content Manager

For more information about security in Reporting Services, see Using Predefined Roles, Granting Permissions on a Native Mode Report Server and Tasks and Permissions.

Creating and modifying a schedule consists of setting frequency options that determine when the schedule runs.

  • Shared schedules are created as separate items. After they are created, you reference them when defining a subscription or some other scheduled operation.

  • Report-specific schedules are created when you define a subscription or set report execution properties; filling out schedule information is part of defining a subscription or setting properties. To define a report-specific schedule, you open the report or subscription that uses it.

You can create or modify a schedule at any time. However, if a schedule starts to run before you have completed your modifications, the earlier version of the schedule is used. The revised schedule does not take effect until you save it.

If you are modifying a shared schedule, you can pause it before you make changes. The changes take effect when you resume the schedule.

Shared schedules must be deleted manually using the Schedules page in Report Manager or the Shared Schedules folder in Management Studio. If you delete a shared schedule that is in use, all references to it are replaced with report-specific schedules.

Report and subscription-specific schedules are deleted when you delete the report or subscription, or when you choose a different approach to run the report or subscription. For example, choosing Always run this report with the most recent data will delete a report-specific schedule that you created to run a report as a report execution snapshot.

Deleting a schedule and causing it to expire are different. An expiration date is used to stop a schedule but does not delete it. Because schedules are used to automate so many features, they are never deleted automatically. Expired schedules provide evidence to report server administrators as to why an automated process has suddenly stopped. Without the presence of the expired schedule, a report server administrator can misdiagnose the problem or spend unnecessary time trying to troubleshoot a fully functional process.

A report-specific schedule that has expired remains attached to the report. You can determine if a schedule has expired by checking its end date. An expired shared schedules remains in the Shared Schedules list. The Status field indicates whether the schedule has expired. You can reinstate the schedule by extending the end date, or you can remove the schedule reference if you no longer need it.

Was this page helpful?
(1500 characters remaining)
Thank you for your feedback

Community Additions

ADD
Show:
© 2014 Microsoft