Reporting Services/Sharepoint 2013 dynamic Subscriptions.

Question

I am looking for a better solution to this problem.  What I have is about 200 reports and growing that are emailed on some schedule (most once a day as soon as possible). 
This would mean about 200 sql jobs on the RS box, because each subscription create a sql job.  
I am working on a data driven subscription that would create a schedule to run after the DW has finished processing. 
I am noticing I am creating a lot of parameters.  I am also noticing that I will be creating some type of log table.  
Reason is that I need to exec the jobs to run every say 5 min. 
These jobs are looking at the DW log table to show its done and another log table to tell if they have ran or not for the day. 
Thus the actual report will only email one time a day.  
(not sure if someone has a better solution for this).    The solution at this point is create 1 new table to hold parameters that I will use for the subscriptions (for section to define a query to Retrieve Subscriber
data).   The I will need a log table that I would populate once the report is actually sent.  
Thus the real problem I have is that with 200 plus reports all trying to run at the same time. 
In addition to AS trying to process and users all trying to run stuff. 
To help balance this load I would rather have 1 or 2 jobs running on say the reporting services box or even the EDW box that just generates reports.  
This way it runs the reports in a more serial manor.  
I want to get this report from reporting services still.  
What I am really looking for is how to dynamically exec all the pieces needed. 
In other words build a table to hold all 200 reports and the metadata needed from them like format, to, cc, ect… 
Then just create one job on RS that will exec code to loop through each report one at a time and create them. 
I can have n number of job by just creating a grouping as well.
Ken Craig

Answer 1

  The reports run 1x a day so taking the time to cashe them in SSAS or SQL (most come from sql) and then run them again in SSRS has just added load with no value.   Why hammer anything. 
I have been digging more but still looking.  What I have found is that a job just loads a records into a table called AddEvent.  Something that picks up a record from that and runs it.  From what I can tell it uses the @eventdata to get the
information out of the Subscriptions and Catalog table. 
Not sure if I am on the right path but still thinking I need to take the 200 plus reports and load them into a table.  This would be all parameters and all subscription info.  Then have maybe just a couple jobs.  Example one job runs 175 reports
and other runs 25.  I can group them how I like or add more jobs as I need to.  Including creating an order for them.  This way one job will run serial.  Thus allowing me to control the load on the SQL box and SSAS box.  Instead of
having 200 queries all slamming sql server and/or SSAS at the same time.
Ken Craig