Hi All,We are having a bit of a disagreement of where to install reporting services within work, and i would like some input.Basically there are two views.1. We leave reporting Services running on one of our current servers, and reference it through the report viewer, using http. I think the firewall is setup to do this internally. The websites will then use the control to access the reports.2. We have reporting services on our external DMZ where all our websites reside.I have argued for number 1, becuase mainly of memory usage and problems it can cause to servers performance wise.Anyone else got any ideas?Cheers, Nick

It all depends on so many factors. This article should help you in getting to a conclusion.http://download.microsoft.com/download/1/3/4/134644fd-05ad-4ee8-8b5a-0aed1c18a31e/rs_scalability.doc HTH

Thanks for the response. Ive had a quick scan of that document, and i understand that splitting the catalog from the server should be done, though it is not clear on if i should host my report server on the same server as my webpages. We have many sites using reporting services, and i have 1 report that can take up a huge amount of resources and am a little bit worried about how the resource usage will affect website performance. What do you recon? Cheers, Nick

since you have many sites using reporting services, can you afford to have a dedicated report server (no other web sites in this machine)? This way in the future you can add more report severs (scale-out scenario) based on the need.

Well that kind of what we have with the report server sat on a different server, we actually have the report server sat on two boxes at present. Do you think that if it is installed locally to the DMZ i.e. where all our external webservices and web application are hosted, we are limiting our the scalability? The other argument that was brought up is one of security, Because we reference our report servers like http://<servername>/reportserver from the DMZ one of the developer feels that this poses a security risk, as we need to use port 80 even though you need an account in active directory to use the report server.

Hi, I have similar scenario. I have one dedicated web server for external users and one application server for services and middle layer. As SSRS 2008 R2 doesn't require IIS hence I think installing reporting services on application server and the catalog databases on DB server will be good approach. Pl note - Our application server doesn't have IIS. Any other thought? Thanks,- JL