January 25, 2016 at 4:21 pm
Hi,
We have a SQL Server 2014 Cluster setup on Windows server 2012 (This is named instance).
Initially while selecting the features, I didn't choose the Integration services. Later I added. While doing the adding features it throw me error when I select the existing instance name.
I run the setup file on Node A and choose as new installation and selected the SSIS and same way I did on node B and later selected the configuration file on both nodes pointing to the named instance (existing clustered).
Incase if we want to the SSIS cluster, How to do?
What will be the issues with doing SSIS clustering
January 26, 2016 at 2:34 am
From Integration Services (SSIS) in a Cluster- SQL Server 2014:
Clustering Integration Services is not recommended because the Integration Services service is not a clustered or cluster-aware service, and does not support failover from one cluster node to another. Therefore, in a clustered environment, Integration Services should be installed and started as a stand-alone service on each node in the cluster.
The article goes on to say you can manually change it to a cluster resource after install, but again, it is not recommended.
There are no special teachers of virtue, because virtue is taught by the whole community.
--Plato
January 27, 2016 at 3:26 pm
How the SSIS packages deployments works in SQL 2014.
Do the developers provide the packages to DBA for the deployments?
January 27, 2016 at 6:03 pm
You can read about the different deployment models for SSIS, Package and Project, in Books Online.
As for how they get deployed to a production setting, eg by sending to a DBA for review amd deployment, that is a choice your orgamization's leadership needs to make.
There are no special teachers of virtue, because virtue is taught by the whole community.
--Plato
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply