While performing a new installation of SQL Server 2012 on
a Windows 2012R2 cluster, I learned a few things along the way and I want to
share them with you.
There are 3 main area to watch out when building the
cluster and SQL Server
1. Integration
Services (SSIS) is not cluster aware. You can get SSIS working in the cluster. However,
if you have a SSIS package that is executing and the cluster fails over (from
active to passive node) the SSIS package will not continue to execute. In fact
you have to restart the SSIS package execution. Therefore you need to build
some logic in you package to detect if the SSIS package execution was completed
or not and if not, who to roll back the changes and re execute it. There is
also a fix to allow remote connection to SSIS which can break too
2. Reporting
Services (SSRS) will not start after applying patches. It appears that the
patch can/does break SSRS but it’s an easy fix
3. Always
On Availability Groups does not work between clusters. That is, if you have a
cluster (say 2 nodes) and you want to replicate with Always On Availability
Groups to another cluster (again say a 2 node cluster), this will not
work! There is no documentation from Microsoft support about this. So be aware
of this limitation
Below are the links that help with the issues notes above
and others I found useful when building a Windows 2012R2 cluster and SQL Server
2012.
Integration
Services (SSIS) in a Cluster is not Cluster Aware
Configure
the Integration Services Service as a Cluster Resource
Grant
Access to the Integration Services Service
Connect
to a Remote Integration Services Server
Cannot
Start SQL Server Reporting Services after applying an update
Before
Installing Failover Clustering
SQL
Server Failover Cluster Installation
Create
a New SQL Server Failover Cluster (Setup)
Error
during Installation of an SQL Server Failover Cluster Instance
Please let me know if you find any other useful
information and/or links in this topic.
Thanks and enjoy.
Rudy