Running SSIS package on server other than SQL Server

SQLServerCentral is supported by Red Gate Software Ltd.

Popular Topics

Home

Members

Calendar

Who's On

Home » SQL Server 2005 » SQL Server 2005 Integration Services » Running SSIS package on server other than SQL...

Running SSIS package on server other than SQL Server

Rate Topic

Display Mode

Topic Options

Author

Message

Girish Bhat

Posted Monday, April 19, 2010 1:08 AM

SSC Veteran

Group: General Forum Members
Last Login: Friday, February 22, 2013 1:02 AM
Points: 206, Visits: 425

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?

Thanks!

Post #905734

Koen Verbeeck

Posted Monday, April 19, 2010 2:02 AM

SSCrazy Eights

Group: General Forum Members
Last Login: Today @ 6:51 AM
Points: 9,372, Visits: 6,470

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

How to post forum questions.
Need an answer? No, you need a question.
What’s the deal with Excel & SSIS?

Member of LinkedIn. My blog at LessThanDot.

MCSA SQL Server 2012 - MCSE Business Intelligence

Post #905748

Elliott Whitlow

Posted Monday, April 19, 2010 9:36 AM

SSCertifiable

Group: General Forum Members
Last Login: Wednesday, April 24, 2013 12:02 PM
Points: 5,854, Visits: 4,873

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.

CEWII

Post #906094

Girish Bhat

Posted Monday, April 19, 2010 10:06 PM

SSC Veteran

Group: General Forum Members
Last Login: Friday, February 22, 2013 1:02 AM
Points: 206, Visits: 425

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

Post #906484

« Prev Topic | Next Topic »

Permissions