Reporting Services/Sharepoint 2013 dynamic Subscriptions.


i looking better solution problem.  what have 200 reports , growing emailed on schedule (most once day possible).  this mean 200 sql jobs on rs box, because each subscription create sql job.   i working on data driven subscription create schedule run after dw has finished processing.  i noticing creating lot of parameters.  i noticing creating type of log table.   reason need exec jobs run every 5 min.  these jobs looking @ dw log table show done , log table tell if have ran or not day.  thus actual report email 1 time day.   (not sure if has better solution this).    the solution @ point create 1 new table hold parameters use subscriptions (for section define query retrieve subscriber data).   the need log table populate once report sent.  

thus real problem have 200 plus reports trying run @ same time.  in addition trying process , users trying run stuff.  to balance load rather have 1 or 2 jobs running on reporting services box or edw box generates reports.   this way runs reports in more serial manor.   want report reporting services still.   looking how dynamically exec pieces needed.  in other words build table hold 200 reports , metadata needed them format, to, cc, ect…  then create 1 job on rs exec code loop through each report 1 @ time , create them.  i can have n number of job creating grouping well.


ken craig

you setup caching report , have cache refresh plan cache plan time dw finishes processing, reports won't hammer ssas, hammer ssrs, faster.  snapshots option.


SQL Server  >  SQL Server Reporting Services, Power View



Comments

Popular posts from this blog

Conditional formatting a graph vertical axis in SSRS 2012 charts

Register with Power BI failed

SQL server replication error Cannot find the dbo or user defined function........