Reporting Services initial application design question

I am new to Reporting Services, and I would like to serve up SQL 2005 Reporting Services reports via an ASP.NET web app (possibly using Report Viewer controls in Server mode).The web app will be running on an IIS server outside the firewall.

I would prefer to have the Reporting Services server be inaccessible outside the firewall, but it seems that the client browsers need direct URL access to the Reporting Services server.I guess this means either locating the Reporting Services server outside the firewall, or opening a hole in the firewall for access to the Reporting Services server.

Is there a Microsoft best-practice methodology/white-paper that addresses this scenario (especially as regards security concerns)?

Alternately, would it be possible, and would the same report presentation functionality be available (reports with expanding/collapsing sections, choice of export formats, etc), by calling the Reporting Services web service directly from the ASP.NET app, and manually populating the Response object?

Thanks.Any help would be appreciated.

Here is a posting that may help your scenario.

http://blogs.msdn.com/tudortr/archive/2005/11/03/488731.aspx

cheers,

Andrew

|||

Thanks for your response. I had found that link previously, but I've since found another idea that sounds promising:

Extending SQL Server Reporting Services with SQL CLR Table-Valued FunctionsExtending SQL Server Reporting Services with SQL CLR Table-Valued Functions http://msdn2.microsoft.com/en-us/library/bb293147.aspx