I am a windows admin with intermediate knowledge of SQL Server and its components like SSRS. Anyway, I built a production SQL2008 cluster successfully. The head developer also wanted to install SSRS2008 on one of the nodes along with a custom .NET framework
Needless to say I did get SSRS2008 installed on the active node, but starting having problems with the cluster services and other strange happenings. So I removed SSRS2008 from the node and created a VM, installed SSRS2008 ENT(gonna have to uninstall/reinstall
Standard) on that and created the databases via the config wizard and this vm is also running the custom .NET framework application. All of the DBAs agreed that this should have not been installed on the cluster.
Now I have to justify why I did this......
1. For a Production cluster environment isn't is suggested to have ssrs installed on a separate server with it's database housed on the cluster? ( I was told this was an "old school" way of thinking by the developer).
2. Is having SSRS installed on one node of the cluster supported by Microsoft?
In my humble opinion, a database cluster is meant for housing databases only for high availability and nothing else should be present on these two nodes.
Is there any documentation for SSRS that suggests the seperate server deployment rather than including t
View Complete Post