SQL Server Performance

Running SSIS Packages from remote server

Discussion in 'SQL Server 2005 Integration Services' started by kasaranenikiran, Jan 12, 2010.

  1. kasaranenikiran New Member

    In our existing environment, We have SQL 2005 and Varicent Tool on same box. We have specific SSIS Packages which were put in a batch files and scheduled from Varicent Tool.
    But, In the new environment, we have put SQL 2005 on a different machine and Varicent on different machine. But, we still need to run those batch files to be scheduled and run from Varicent ( which does not have SQL Server on it ).
    Is there a way we can do this ?? Suggestions Please .
  2. MohammedU New Member

    I believe you need to install SSIS to run the package from the remote server but you can create a job on the destination server with the ssis package you wnat to execute and then star the job using the batch file.
    And also check DTExec utitlity...
  3. LouisP New Member

    Just keep in mind that a SQL Server license is required even just to run SSIS. This was not the case in 2000, where at best, a CAL was all that was needed if the SQL Server being conencted to wasn't processor licensed.
  4. satya Moderator

    Welcome to the forums
    In addition, you can design packages that are able to execute SSIS packages on remote SQL Server systems by using the Execute SQL Server Agent task which is found in the SSIS Designer toolbox under the Maintenance Plan tasks section.
    When you add the Execute SQL Server Agent task to the SSIS Designer, you can set its Connection properties to point to the remote server. Then when the task is executed, the SQL Server Agent will execute a package on the remote machine

Share This Page