The way Reporting Services creates subscriptions is through generating a SQL Server Agent job. This is apparent when you look at the jobs on the database server that Reporting Services is configured to use. At any rate, when the jobs are created, they are named with a very hard to determine GUID. Here is a quick sample query how you might get some of the “Report Names” to match the “jobs”.

SELECT

      c.Name AS ReportName

      , rs.ScheduleID AS JOB_NAME

      , s.[Description]

      , s.LastStatus

      , s.LastRunTime

FROM

      ReportServer..[Catalog] c

      JOIN ReportServer..Subscriptions s ON c.ItemID = s.Report_OID

      JOIN ReportServer..ReportSchedule rs ON c.ItemID = rs.ReportID

      AND rs.SubscriptionID = s.SubscriptionID

I sent a query out like this last year to a friend of mine and a recent post reminded me of it. So I thought that I would post it here for everyone to find (especially me as I had to quickly search through my emails) 🙂 Thankfully, I knew exactly who I sent it to.

As always, you can follow me on twitter using @briankmcdonald