I have a 2 node SQL Server 2005 64bit clustered. I was able to configure SSIS as a clustered resource with the packages stored in shared storage and the .ini modified along with the registry change. All works fine, however, when the resource
failsover, the SSIS Server Service is already running on the other node. It doesn't pickup the SSIS Packages on the File System or MSDB, until the SSIS Server Service is Restarted.
Is there a way to make that restart automatically when the resource failsover? The Restart Policy on the Advance Tab of Cluster Admin doesn't make the service restart if it's already running.
Is this how SSIS in a cluster works as a best case scenario? Any suggestions?
View Complete Post