We help IT Professionals succeed at work.

Run SSIS package on another computer

hungoveragain
on
I have a problem when trying to run a SSIS package on a remote computer. Let's say I have two computers 1.2.3.4 and 4.3.2.1

My SQL server instance is on 1.2.3.4 and there is a firewall opening on 4.3.2.1 to an external machine. The SSIS package extracts files from the db, places them on 4.3.2.1 then opens WinSCP to ftp those files to the external machine.

The SSIS package is on \\4.3.2.1\d$\somefolder\ssispackage.dtsx

When I run the package on 4.3.2.1 there is no problem with database connectivity or FTP connectivity, however when I set the package to run through the SQL Server Agent and connect to the above file I am told that it can't find WinSCP.

What I am taking this to mean is that 1.2.3.4 is running the SSIS package it finds on 4.3.2.1, but because WinSCP doesn't exist on 1.2.3.4 it is falling over. While I can install WinSCP on 1.2.3.4 to get this to work it would be pointless because the firewall is closed here.

How can I run the package on 4.3.2.1, but ensure that it is 4.3.2.1 that is running the package?

Thanks

MIke
Comment
Watch Question

Marten RuneSQL Expert/Infrastructure Architect

Commented:
Use a scheduled task to run the pachage on 4.3.2.1

//Marten
SQL Expert/Infrastructure Architect
Commented:
The above comment takes for granted that you don't have a SQL Server installed on 4.3.2.1. If you do, then a schedules sql agent task would be the normal way to do it.

But...
As you descriibe it, you can fire the package manually. Just use this credentials, and the same command in a scheduled task and you're home.

Regards Marten

Author

Commented:
Can you please be more specific? How do I run a DTSX task in windows scheduler?

Thanks

Mike

Author

Commented:
Never mind - I have managed it - thanks.

Mike