|
|
|
SSCommitted
      
Group: General Forum Members
Last Login: Thursday, May 16, 2013 8:24 AM
Points: 1,610,
Visits: 590
|
|
As a prod DBA I've been a bit snobby and dismissive of SSIS in the past (even preferring DTS!) but with some clients I've had no choice but to get right in there and debug failing SSIS packages, but I will conceed it's a good feeling when you get them working. Will be following this series closely, knowledge is power and all that. 
qh
SQL 2K acts like a spoilt child - you need to coax it round with lollipops.
|
|
|
|
|
Forum Newbie
      
Group: General Forum Members
Last Login: Tuesday, April 23, 2013 8:53 AM
Points: 5,
Visits: 28
|
|
Hey Andy, I'm just coming into the world of SSIS and I'm fighting my corporate DBA's about it.
Can you answer a fundamental question? And I know this probably isn't a good place for this, but...
If I install SSIS on a server that doesn't have SQL Server on it, just SSMS, do I need a full SQL license just to use SSIS to convert some DTS packages? They will eventually run on SQL2008, but we're waiting on the new servers at this point.
Based on lots of postings, I don't believe so. And Microsoft literature seems to be contradictory on the matter.
Thanks Greg
|
|
|
|
|
Forum Newbie
      
Group: General Forum Members
Last Login: Tuesday, April 23, 2013 8:53 AM
Points: 5,
Visits: 28
|
|
Hey Andy, I'm just coming into the world of SSIS and I'm fighting my corporate DBA's about it.
Can you answer a fundamental question? And I know this probably isn't a good place for this, but...
If I install SSIS on a server that doesn't have SQL Server on it, just SSMS, do I need a full SQL license just to use SSIS to convert some DTS packages? They will eventually run on SQL2008, but we're waiting on the new servers at this point.
Based on lots of postings, I don't believe so. And Microsoft literature seems to be contradictory on the matter.
Thanks Greg
|
|
|
|
|
Old Hand
      
Group: General Forum Members
Last Login: Monday, May 13, 2013 2:53 PM
Points: 375,
Visits: 947
|
|
Hi Greg,
You can develop SSIS using Business Intelligence Development Studio (for 2005, 2008, and 2008 R2) or SQL Server Development Tools (for 2012) on any server with the workstation tools installed. You cannot execute packages outside the development environment without a SQL Server relational engine license. For this reason, I refer to SSIS as "free" (in double-quotes).
Hope this helps, Andy
Andy Leonard CSO, Linchpin People Follow me on Twitter: @AndyLeonard
|
|
|
|
|
Forum Newbie
      
Group: General Forum Members
Last Login: Tuesday, April 23, 2013 8:53 AM
Points: 5,
Visits: 28
|
|
Hey Andy, Thanks for the reply. That was how I read all of the Microsoft doc, but our "software police" seem to insist that a SQL license/install accompany BIDS or SSIS on any machine, which makes no sense to me.
I can attach to whatever servers I need to, develop the packages on SSMS on my workstation, and then install/store them on the actual server where they need to live, as I see it. And it sounds like that's what you're saying too.
OK, many thanks. This is all pretty new to me, compared to stored procedures. Just haven't had the need to get too heavily into it before.
Thanks again. Greg
|
|
|
|
|
Old Hand
      
Group: General Forum Members
Last Login: Monday, May 13, 2013 2:53 PM
Points: 375,
Visits: 947
|
|
Hi Greg,
That is what I am saying, yes. You can develop SSIS packages on any machine just by installing the Microsoft Business Intelligence components. As far as I know, the same licensing applies to SSMS.
Hope this helps, Andy
Andy Leonard CSO, Linchpin People Follow me on Twitter: @AndyLeonard
|
|
|
|