InstantForum.NET v2.9.0SQLServerCentralhttp://www.sqlservercentral.com/Forums/notifications@sqlservercentral.comSat, 25 May 2013 02:48:58 GMT20http://www.sqlservercentral.com/Forums/Topic1401936-364-1.aspxok, thank you both for your input.Thu, 03 Jan 2013 08:20:34 GMTgwgellerhttp://www.sqlservercentral.com/Forums/Topic1401936-364-1.aspx[quote][b]Steve Jones - SSC Editor (1/2/2013)[/b][hr]There isn't a way to do this. While SSIS is a separate part of SQL Server and can be deployed without the database engine, you cannot use the redistributable parts of SSIS, AFAIK, without having a SQL Server 2012 license.You could purchase an SE license, as few cores/CALs as needed to run things.[/quote]Yup, I'd just get the standard edition to run it. But a 2012 license is required.Wed, 02 Jan 2013 22:29:27 GMTSQLRNNRhttp://www.sqlservercentral.com/Forums/Topic1401936-364-1.aspxThere isn't a way to do this. While SSIS is a separate part of SQL Server and can be deployed without the database engine, you cannot use the redistributable parts of SSIS, AFAIK, without having a SQL Server 2012 license.You could purchase an SE license, as few cores/CALs as needed to run things.Wed, 02 Jan 2013 10:31:20 GMTSteve Jones - SSC Editorhttp://www.sqlservercentral.com/Forums/Topic1401936-364-1.aspxThank you for the reply. Basically we need the new features in SSIS, not Sql server. So if there is a way to avoid having to buy a full version of Sql server 2012 just to utilize SSIS 2012 please let me know.Wed, 02 Jan 2013 10:18:46 GMTgwgellerhttp://www.sqlservercentral.com/Forums/Topic1401936-364-1.aspxYou cannot deploy a 2012 package to SQL Server 2005.However, you can use SQL Server 2005 in your connection manager. But the package must be run from SQL 2012.Wed, 02 Jan 2013 10:09:56 GMTSQLRNNRhttp://www.sqlservercentral.com/Forums/Topic1401936-364-1.aspxHello all, We work alot with mysql and will only be doing more, although sql server will remain prevalent. We utilize SSIS, and even DTS still, to move our data around. Problem is working with mysql in SSIS 2005 is a pain and now I've run into a situation where it might take a bunch of hacks. So I read that 2012 will take care of a few issues I'm having. Mainly actual ODBC sources and destinations, and no 4000 character expression limit.We have several sql server 2005 instances running already. I see that a sql server development license is really cheap. So I have two questions. If I were to purchase a 2012 sql server developer license...1. Would the license allow me to develop 2012 version packages and deploy them to a 2005 instance?2. Would a 2012 package run using 2005 sql server? I plan on running the packages from the file system using sql agent.Thanks,GGWed, 02 Jan 2013 09:55:17 GMTgwgeller