Return to Question

I am planning a sql server installation with fci.

There will be 2 sql server 2019 instances in active/passive mode; they share the same SAN.

This question is about ssis.

Link: https://learn.microsoft.com/en-us/sql/integration-services/service/integration-services-ssis-in-a-cluster?view=sql-server-ver15

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.

Integration services is a shared feature that I usually (in a non-fci based installation) select from the features page when installing the sql server database engine.

This is the 1st time I am going to install database engine and integration services in a fci environment, so I want to ask: What does installed and started as a stand-alone service in the above quote mean? Does it mean that I should first configure the fci and 2 sql server instances (I1 and I2, ofcourse on 2 nodes) without integration services, and then create 2 new instances (I3 on node1 and I4 on node2) of sql server with database engine and integration services?

If so then do I have to deploy all my ssis packages on both the ssis based instances?

This means the FCI is only targetting the I1 and I2 database engine for failover?

I am planning a sql server installation with fci.

There will be 2 sql server 2019 instances in active/passive mode; they share the same SAN.

This question is about ssis.

Link: https://learn.microsoft.com/en-us/sql/integration-services/service/integration-services-ssis-in-a-cluster?view=sql-server-ver15

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.

Integration services is a shared feature that I usually (in a non-fci based installation) select from the features page when installing the sql server database engine.

This is the 1st time I am going to install database engine and integration services in a fci environment, so I want to ask: What does installed and started as a stand-alone service on each node in the above quote mean? Does it mean that I should first configure the fci and 2 sql server instances (I1 and I2, ofcourse on 2 nodes) without integration services, and then create 2 new instances (I3 on node1 and I4 on node2) of sql server with database engine and integration services?

If so then do I have to deploy all my ssis packages on both the ssis based instances?

This means the FCI is only targetting the I1 and I2 database engine for failover?

I am planning a sql server installation with fci.

There will be 2 sql server 2019 instances in active/passive mode; they share the same SAN.

This question is about ssis.

Link: https://learn.microsoft.com/en-us/sql/integration-services/service/integration-services-ssis-in-a-cluster?view=sql-server-ver15

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.

Integration services is a shared feature that I usually (in a non-fci based installation) select from the features page when installing the sql server database engine.

What does installed and started as a stand-alone service mean? Does it mean that I should first configure the fci and 2 sql server instances (I1 and I2, ofcourse on 2 nodes) without integration services, and then create 2 new instances (I3 on node1 and I4 on node2) of sql server with database engine and integration services?

If so then do I have to deploy all my ssis packages on both the ssis based instances?

This means the FCI is only targetting the I1 and I2 database engine for failover?

I am planning a sql server installation with fci.

There will be 2 sql server 2019 instances in active/passive mode; they share the same SAN.

This question is about ssis.

Link: https://learn.microsoft.com/en-us/sql/integration-services/service/integration-services-ssis-in-a-cluster?view=sql-server-ver15

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.

Integration services is a shared feature that I usually (in a non-fci based installation) select from the features page when installing the sql server database engine.

This is the 1st time I am going to install database engine and integration services in a fci environment, so I want to ask: What does installed and started as a stand-alone service in the above quote mean? Does it mean that I should first configure the fci and 2 sql server instances (I1 and I2, ofcourse on 2 nodes) without integration services, and then create 2 new instances (I3 on node1 and I4 on node2) of sql server with database engine and integration services?

If so then do I have to deploy all my ssis packages on both the ssis based instances?

This means the FCI is only targetting the I1 and I2 database engine for failover?

I am planning a sql server installation with fci.

There will be 2 sql server 2019 instances in active/passive mode; they share the same SAN.

This question is about ssis.

Link: https://learn.microsoft.com/en-us/sql/integration-services/service/integration-services-ssis-in-a-cluster?view=sql-server-ver15

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.

Integration services is a shared feature that I usually select in the features page when installing the sql server database engine.

What does installed and started as a stand-alone service mean? Does it mean that I should first configure the fci and 2 sql server instances (ofcourse on 2 nodes) without integration services, and then create a new instance of sql server with database engine and integration services on both the nodes?

If so then do I have to deploy ssis packages on both instances?

I am planning a sql server installation with fci.

There will be 2 sql server 2019 instances in active/passive mode; they share the same SAN.

This question is about ssis.

Link: https://learn.microsoft.com/en-us/sql/integration-services/service/integration-services-ssis-in-a-cluster?view=sql-server-ver15

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.

Integration services is a shared feature that I usually (in a non-fci based installation) select from the features page when installing the sql server database engine.

What does installed and started as a stand-alone service mean? Does it mean that I should first configure the fci and 2 sql server instances (I1 and I2, ofcourse on 2 nodes) without integration services, and then create 2 new instances (I3 on node1 and I4 on node2) of sql server with database engine and integration services?

If so then do I have to deploy all my ssis packages on both the ssis based instances?

This means the FCI is only targetting the I1 and I2 database engine for failover?