Subscriptions in Reporting Services are designed to run on a schedule and there isn?t a built-in feature to just run a subscription manually.
This is actually quite easy to do with a little bit of TSQL or .NET programming code. You can either use the SSRS web service API via code or command line script, or run the SQL Agent job using the sp_start_job system stored procedure. In either case, you will need the SubscriptionID GUID assigned to the SQL Server Agent job that was generated when the subscription was created. This is stored in the ReportServer Subscriptions table. Each SubscriptionID has a corresponding SQL Server Agent job named using the same GUID.
To find the subscription Agent jobs, open SQL Server Management Studio and connect to the relational instance hosting the report server content databases. Expand the SQL Server Agent jobs. Each job will have one step and will be scheduled to run at the time specified in Report Manager. Subscriptions have a TimedSubscription event type and reference the report?s ItemID key in the ReportServer database Catalog table. Hopefully, the can find this just be using the scheduled execution time. Copy the job name GUID to the clipboard. Do not modify this job or step but .
After you have the SubscriptionID/Job name, running the subscription is the easy part. In a T-SQL script, just execute this command substituting the GUID:
USE msdb
EXEC sp_start_job @job_name = ‘D4EF7E0D-7FFB-47A5-A87A-D63F2D242A06’
You can use an ADO.NET SqlCommand object to execute this code from web form or application.
The programmatic technique uses the SSRS web service API or the rs command line utility (which is actually a console wrapper around the web service interface). Using the command line option, the FireEvent method with the TimedSubscription argument will start the subscription using the Agent job name GUID:
Dim rs As New ReportingService()
rs.Credentials = System.Net.CredentialCache.DefaultCredentials
rs.FireEvent(“TimedSubscription”, “D4EF7E0D-7FFB-47A5-A87A-D63F2D242A06”)
AWESOME! Thanks so much for the tip!
THANK YOU THANK YOU THANK YOU…. I have been hitting my head on the wall trying to resolve how I could run a sub on the 3rd business day of each month and this was the final piece to the puzzle.
Thank You so much for addressing this issue! Should note that if you have permissions to the reporting services database, you can query it to more easily identify the Subscription/ScheduleID(s) that you need.
http://blogs.msdn.com/b/deanka/archive/2009/01/13/diagnosing-and-troubleshooting-subscriptions.aspx