Hi, multipart questions.
We have a SQL 2008 Cluster where we do not want to install SSIS. We have a SQL 2005 SSIS instance on another server for packages.
1. Can we configure jobs on the SQL 2008 custer to point to the 2005 SSIS instance? and do we need SSIS installed on the SQL 2008 cluster to do this?
2. Can we run jobs on a SQL 2005 instance, pointing to a SQL 2005 SSIS instance/packages on a third server that connect to a SQL 2008 DB instance . I know that sounds crazy, but where exactly is the CPU and memory load in that design.. job on one server,
package a seperate server and db on a third server.?
3. As mentioned, I have SQL 2005 SSIS instance. I have local admin on that server and can connect to the ssis instance from my sql 2005 sql client on my desktop. I added a new user to the server and added them to the SSIS and users group. I also
made sure they could write to the folder where they will deploy packages. However, they get some kind of access denied while trying to connect, unless I give them local admin on the server. What more access do they need than to be in the users and SSIS
group and have write access to an SSIS deployment folders?
View Complete Post