I have completed this task for my client during this weekend and wanted to update you on the trick that I learnt. As we know that to add any features like SSIS and reporting service is very easy task, but if we have to do the same in exiting cluster environment in live production server then the game is different . As a precaution we should take the backup for all user and system databases .To do the same kind of step In setup’s SQL Server Installation Center we naturally select “New SQL Server stand-alone installation or add features to an existing installation”, because we already have a installed instance of SQL Server on the cluster.
In the “Installation Type” step of the setup, if we select the second ratio button to “Add features to an existing instance of SQL Server” is when we run into problems in this situation.
If we select the “Integration Services” option only during the “Feature Selection” step, then proceed with the SSIS installation we will encounter the following error if we already have a clustered SQL instance:
Rule “Existing clustered or cluster-prepared instance” failed.
The instance selected for installation is already installed and clustered on computerSQLClustInstName. To continue, select a different instance to cluster.
Of course, we don’t want to install another cluster to wer instance, but here is the key: we have to choose “Perform a new installation of SQL Server 2008”, which is the first radio button in the Installation This will allow us to select any feature we desire to put on the system in the Feature Selection step:
Here we would only select “Integration Services” By just choosing “Integration Services” we can successfully install SSIS on each node of the cluster. We must run this setup on all nodes of the cluster where we want the SSIS service installed.
We should not forget <ServerName>.\SQL2008</ServerName> property in the MsDtsSrvr.xml file to correctly point to wer SQL virtual server name rather than the default “.\InstanceName” that is currently there.