I have a web application built as a way to search through invoices, summaries, and work orders. In short, when a user drills down to a specific invoice, summary or work order, they may hit a print button, which launches a sql reporting services report.

Please avoid commenting on the obvious architectural flaws, as I could just use a stylesheet w/ media set to print to format the drilled-down invoice, summary or work order, because my boss insisted I use sql reporting services.

Nevertheless, I built the damn thing. Works great.

However, for deployment, we're throwing the app on one web server box, and the database on another.

My boss has just one sql server license, and, as you may know, sql reporting services is a part of the server install. So, sql reporting services must reside on the database server.

The problem is that sql reporting services makes a web app for itself only on the local IIS. Because I simply will not point traffic to the database server, I need help.

Here is a link that might help:

http://www.microsoft.com/technet/prodtec...

You can connect to a remote instance of SQL Server via the Report Server. I have an instance of report server running on a web server that just grabs data from a remote SQL server. I think I configured it when I initially ran setup and it created the reportserver databases. If you rename or move the databases after setup, you must run the Rsconfig.exe utility to update the connection information.

Anyway, I got all the info I needed to figure it out from MS websites.