InstantForum.NET v2.9.0SQLServerCentralhttp://www.sqlservercentral.com/Forums/notifications@sqlservercentral.comTue, 21 May 2013 23:03:38 GMT20http://www.sqlservercentral.com/Forums/Topic905734-148-1.aspxThanks a lot for your reply.. This is exactly what I was looking for!Mon, 19 Apr 2010 22:06:27 GMTGirish Bhathttp://www.sqlservercentral.com/Forums/Topic905734-148-1.aspx1. 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.CEWIIMon, 19 Apr 2010 09:36:27 GMTElliott Whitlowhttp://www.sqlservercentral.com/Forums/Topic905734-148-1.aspxNot 100% sure, but I believe you need the Integretion Services service to run packages. And for that, you need SQL Server...Mon, 19 Apr 2010 02:02:23 GMTKoen Verbeeckhttp://www.sqlservercentral.com/Forums/Topic905734-148-1.aspxCan 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!Mon, 19 Apr 2010 01:08:04 GMTGirish Bhat