A company runs SQL Server Database Engine and SQL Server Reporting Services (SSRS) in native mode. Reports are based on data that is cached in multiple shared datasets. Source data is archived each…

The FlushCache method exposed by the MSReportServer_ConfigurationSetting WMI class allows a script to programmatically and selectively clear cached shared dataset results for individual items; this script can be invoked by a SQL Server Agent job timed after midnight, providing a fully automated solution that targets only the stale cache without any service interruption or dependency on shared schedules that may be paused during maintenance windows.

Directly truncating tables in the SSRS ReportServer catalog database bypasses the Reporting Services API entirely and can corrupt internal metadata, configuration state, and report history - this approach is unsupported by Microsoft.

Restarting the SSRS Windows service does clear all in-memory cache but causes a service outage affecting all active report consumers and is an overly disruptive, non-targeted approach for a nightly cache invalidation requirement.

Creating a shared schedule alone has no cache-clearing effect; it only defines a timing trigger that must be explicitly attached to a cache expiration policy on individual datasets, and the scenario states shared schedules are paused during the relevant maintenance window.