Running SSIS package on server other than SQL Server

  • Can an SSIS package execute on a server other than the database machine. I mean, is it possible to install some kind of client package on a computer where SQL Server 2005 is not installed and execute packages on this machine? What would be the licensing implications in case it is possible?


  • Not 100% sure, but I believe you need the Integretion Services service to run packages. And for that, you need SQL Server...

    Need an answer? No, you need a question
    My blog at
    MCSE Business Intelligence - Microsoft Data Platform MVP

  • 1. SSIS can be installed seperately from SQL Server. You basically ONL choose SSIS when you do the install.

    2. Licensing is STEEP, SSIS is NOT licensed seperately, you are basically burning a FULL sql license to install SSIS (or SSAS or SSRS, etc.) all by itself.

    3. This basically limits you to using the file system to store packages unless you configure it to look at a SQL Server elsewhere where packages could be stored.

    I have some experience with this config and have typically installed a SQL instance as well to support SSIS and do scheduling of packages locally. No non-system databases were installed.

    This config is more typical with large organizations trying to limit where ETL is happening and get better visibility. I haven't seen many small organizations do it because of the cost.


  • Thanks a lot for your reply.. This is exactly what I was looking for!

Viewing 4 posts - 1 through 4 (of 4 total)

You must be logged in to reply to this topic. Login to reply