October 28, 2011 at 12:01 pm
I am relatively new to the marvelous world of SQL and I have a question about best practices when it comes to reporting services. What I would like to do ,and in my novice mind makes sense, is create a centralized SQL Reporting Server and have my users all got to the same portal to process their SQL reporting. (i.e. https:\\mysqlreportingserver) I am wanting to do this so that we have one place where our tier 2 and tier 3 SQL users can go for reports. Is this best practices and are there any specific things to consider in order for this to work. Thanks.
October 28, 2011 at 1:37 pm
While I generally like the idea it is important to also think about what happens when that server becomes bogged down and starts performing poorly. Are you going to do a scale out (add another server connected to the same set of SSRS databases which is only supported on EE) or a scale up (add memory, CPU basically) or what I like to call a poor man's scale out, add another server that has all the same reports/datasources but you have to maintain them manually. With two servers you might consider the use of some kind of load balancing.
It is also important to think about licensing. If you install SSRS on another server you have to license SQL for that server. When you license SQL you are licensing a machine effectively not the individual components. The same is true if you install SSAS, SSRS, SSIS, and the engine all separately you would need 4 licenses.
CEWII
Viewing 2 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply