Reporting server setup

  • I would like to check with other DBAs in the forum, when you setup a dedicated server for a department, do you usually setup one server with db engine, ssis, ssrs on one box, or you set up at least two: DB server and SSRS server?

    This is a department about 50 people users.

    Since more departments are requesting servers for their own, I would like to put everything in one server if possible good performance to save some resources.

    Previously I usually set up a reporting server besides the user database server.

    The reporting server sometimes are shared by a couple of teams.

    Thanks,

  • This is a slippery slope. What is the reasoning behind each department wanting their own server?

    If they feel that performance would be better, then cost must not be a factor.

    If they want separate servers for security/separation of duties, then there are far more cost effective ways to do this.

    The questions I have is where does the data currently reside? Is the data going to be copied around to each department? See above, I think I would put up a fight on that.

    Based upon the facts, which are few, I would be leaning toward having a central database server where all of the databases live, and separate reporting servers if in fact you have to provide separate servers.

    Sorry, this does not sound like a good idea!!!

    Michael L John
    If you assassinate a DBA, would you pull a trigger?
    To properly post on a forum:
    http://www.sqlservercentral.com/articles/61537/

  • I should make it a little clear. For most of our databases we have a centralized db server and a separate reporting server for example in our IT department.

    But for some other departments they would like to request dedicated server. For example HR department and Special education department.

    The data may come from different sources that used by HR vs Special ed.

    The reason could be for different duties, different down time, different data source, and security, different users.

    It is not all departments, but just a couple of special departments requests like this.

    Other very small applications from small deparment we usually share a database server and a reporting server.

    But for these two, they requested dedicated server for them, so I think to install all components on one server should be good enough for their applications and databases, and reports.

    Thanks,

  • This sounds like the old database server per application scenario, so popular years ago. No longer necessary what with high performance servers of today. Database security can be controlled in many ways, at the database level or within a database by dedicated schemas, HR always tend to be a bit skittish, one possibility is a separate instance, though you would need to capacity plan this scenario.

    Applications and database servers can be separated which is a good move as is a separate reporting server, a whole new set of servers for 50 staff is overkill by the sound of it, unless you are talking about a global internet web service, such as a travel or attractions sight.

    ...

  • At this time, there is no front end web server or application involved. This is mainly used for some database/data manipulation and reports and preparation for state reports that related with either HR or Specical Ed department. They may later have more databases on this same server for their department on their dedicated server, it is not planned for only one database.

    Thanks

  • SSRS security may also be used to provide separation for users within the same SSRS instance.

    no real need for multiple instances or even multiple servers

    -----------------------------------------------------------------------------------------------------------

    "Ya can't make an omelette without breaking just a few eggs" 😉

Viewing 6 posts - 1 through 6 (of 6 total)

You must be logged in to reply to this topic. Login to reply