When I try to deploy an SSIS package to the second instance on my server, I get a nasty message to use the default instance because the service does not support multiple instances.
So, ... just because the "service" won't support multiple instances, does that mean what it sounds like it means, that there is NO WAY for us to put a second (test) instance on the same server and have separate packages in the respective msdb's on each instance?
I mean, that seems to be what it's saying, but here we are, all eager to do just that ... so if there was a way to make it work without the service, we might try it. But maybe dtexec won't even be able to fetch the package from msdb? I don't
want to go so far as to export it manually from the (named instance) msdb to a file just to run it ...
since a cheap workaround is simply to put the dtsx files on a file folder instead of msdb anyway.
(in fact, probably would have been my first choice, if anyone had asked me!)
View Complete Post