installing SSRS 2008 r2 on production Web server - impact, precautions and rollback?
In a two server config where you have a web server and a DB server. Am i correct in presuming it makes most sense to install SSRS on the Web server and not the DB server so we don't end up having sites on the DB server?
The SSRS install notes talk about db instance and root instance location. Does this mater or have any relation to the DBs where SSRS DBs will be hosted?
http://technet.microsoft.com/en-us/library/ms143219.aspx
Any Finally, their is no test environemnt. Some vendor product (web based sites etc) is already runing on the web server and live. Anything to look out for. I'm likely going to have a reboot right? Im looking to see if we can image the
Web server as a precaution.. is this overkill?
Thanks.
============================
Thank You
cyberpine.com
March 16th, 2012 11:22am
Yes, installing SSRS on the Web Server is preferred. The only thing to watch out for is performance. SSRS, depending on what you're doing, can consume quite a bit of CPU and memory while executing reports.
SSRS databases will reside on your SQL Server.http://sharepoint.nauplius.net
Free Windows Admin Tool Kit Click here and download it now
March 16th, 2012 12:24pm
Hi cyberpine,
Thanks for your post.
You can either install SSRS with database engine in the same server, or install them on sperate servers, there is no reboot requirement after you install SSRS on your web server, and it has no affect to the original runing web sites. You can read the articles
below to pay attention to the factors you need to care:
How to: Create a Report Server Database (Reporting Services Configuration)
http://msdn.microsoft.com/en-us/library/ms157300.aspx
Configuring a Report Server Database Connection
http://msdn.microsoft.com/en-us/library/ms159133.aspx
Thanks,
Bill LuBill Lu
TechNet Community Support
March 19th, 2012 5:06am