I have revised this question now that I've determined that we *will* be using the Enterprise edition of SQL Server 2012.
I have a report (that I will deploy to an SSRS 2012 server) which can vary greatly in size. When the report is expected to be small (which we can determine ahead of time by means that are not relevant to this post), it will be rendered by a .NET 4.5 web application using a ReportViewer control (in remote mode).
When the report will be large, we want the web app to "trigger" the report server to generate the report and deposit it as a PDF file or Excel file in a folder on a file share, and then send an e-mail notification to a configured user. Because the reports can be very large, I would prefer not to stream them to the web app and from there to the file share. We have experienced browser timeouts in the past, and so I would prefer to have the SSRS server deposit the generated report directly to the file share.
About 8 parameters have to be passed to the stored procedure which serves as the report’s data source. The database where the stored procedure resides will soon be upgraded to SQL Server 2012.
I am fairly new to reporting services and wanted to ask what approach would be best suited for accomplishing the above-stated goals.
From what I've read so far, I know that one possible approach would be to use data-driven subscriptions but the question then becomes: after inserting report parameters into the subscription table, how does my web app trigger report generation?
Also, I want to deposit the report in a file share and send an e-mail notification to the user. Do I have to create two subscriptions? There is a configuration option when setting up e-mail notification to embed a hyperlink in the e-mail rather than actually include the report in the message. If I select this option, do I give up the ability to specify the destination folder?
