May 1, 2012 at 4:55 pm
I've been reading some of the best practices for configuring OLAP and one of the practices says to install Analysis services as a separate resource of the cluster as the SQL resource. I am going to be installing SQL via an install script and do not see an option for this. Does this mean I need to install SQL Server as a cluster and then come back and install Analysis Services as a named instance after the SQL install? Here is a quick run down of my reqs:
- SQL Server 2008 R2 Enterprise w/SP1
- Windows Server 2008 R2 clustered in Active/Passive
- Replicated Databases from production system must reside on same server as Analysis services per vendor reqs
Any advice from those who have configured SSAS following best practices would be appreciated.
May 1, 2012 at 10:52 pm
If we're going to talk best practices, then SSAS should NOT be on the same server as the database engine. Since the vendor is saying that it is required to be on the same server, you should ask them how they recommend installing it in conjunction with a clustered SQL instance. After all, if you install SSAS as a standalone instance or on it's own cluster, and the active node of SQL is on a different node than SSAS, it's not the same instance. Additionally, if they're requiring SSAS to be on the same server, they may have it coded to connext to the local instance directly, and you can't connect to the local instance of a cluster directly. You have to connect via the virtual name for the cluster.
Their requirements may force you to put SSAS on the same cluster as SQL or may prohibit you from using a cluster at all.
That aside, my reommendation would be to put SSAS on it's own server. And for SSAS, I greatly prefer load balancing over clustering.
May 2, 2012 at 8:11 am
Thanks for the response, I have a meeting today with the vendor a little later today. I know in previous discussions and their Administrative guide this replicated database has to be on the same server as their OLAP databases. I just wasnt sure if there was a way to tie this to a seperate resource group during the install. Sounds like the only way to tie this to a seperate resource is to perform a second install of just SSAS, but as you stated this might cause complications from the vendor side since there is the potential for SQL to be on one node and SSAS on another.
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply