Hello,
I just discovered, while trying to figure out how to cluster SSIS, that the service itself is not cluster aware. However, with proper transaction levels etc. I can get my packages to fail graciously during a node switch.
But at the same time, I just discovered, while reading up on it, that the service itself needs not be installed on the machine for the packages to be created/run/debugged. My question then is the following: if I deploy my packages as files on the hard drive, and not in a package store and run them via SQL Agent, why would I install SSIS if according to Microsoft ( section "There are some tasks...") I don't have to?
I have a feeling there's more to this and I haven't tested more than by just disabling the service and noticing that packages work just as well, but it could be interesting not to have to tell customers that they must install SSIS to run packages.
Thanks,
Greg
I just discovered, while trying to figure out how to cluster SSIS, that the service itself is not cluster aware. However, with proper transaction levels etc. I can get my packages to fail graciously during a node switch.
But at the same time, I just discovered, while reading up on it, that the service itself needs not be installed on the machine for the packages to be created/run/debugged. My question then is the following: if I deploy my packages as files on the hard drive, and not in a package store and run them via SQL Agent, why would I install SSIS if according to Microsoft ( section "There are some tasks...") I don't have to?
I have a feeling there's more to this and I haven't tested more than by just disabling the service and noticing that packages work just as well, but it could be interesting not to have to tell customers that they must install SSIS to run packages.
Thanks,
Greg