<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://sqlblog.com/utility/FeedStylesheets/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>Search results matching tags 'SQL Server 2012' and 'SSIS 2012'</title><link>http://sqlblog.com/search/SearchResults.aspx?o=DateDescending&amp;tag=SQL+Server+2012,SSIS+2012&amp;orTags=0</link><description>Search results matching tags 'SQL Server 2012' and 'SSIS 2012'</description><dc:language>en-US</dc:language><generator>CommunityServer 2.1 SP2 (Build: 61129.1)</generator><item><title>Want to Learn SQL Server 2012?</title><link>http://sqlblog.com/blogs/andy_leonard/archive/2012/10/22/want-to-learn-sql-server-2012.aspx</link><pubDate>Mon, 22 Oct 2012 13:00:00 GMT</pubDate><guid isPermaLink="false">21093a07-8b3d-42db-8cbf-3350fcbf5496:45715</guid><dc:creator>andyleonard</dc:creator><description>&lt;p&gt;Or SSIS 2012? SSRS 2012? SSAS 2012? There’s no substitute for getting your hands on the product, in my opinion.&lt;/p&gt;  &lt;p&gt;I can hear you thinking, “But Andy, I can’t afford to purchase a copy of SQL Server 2012.” Are you sure? What if I told you that you can get a full-feature version of SQL Server 2012 Enterprise Edition for $50? Well, you cannot… it’s actually less than $50! &lt;a target="_blank" href="http://www.amazon.com/SQL-Server-Developer-Edition-2012/dp/B007RFXQAM/"&gt;SQL Server 2012 Developer Edition is available at Amazon&lt;/a&gt; on the day of this writing for $41.24USD. That’s about the price of eight cups of fancy coffee.&lt;/p&gt;  &lt;p&gt;SQL Server releases follow a cycle. SQL Server 2005 was a major release with big changes from SQL Server 2000. SQL Server 2008 and SQL Server 2008 R2 were not drastic departures from SQL Server 2005. Take it from me: SQL Server 2012 is a major release. &lt;/p&gt;  &lt;p&gt;Is taking your career to the next level worth the price of eight cups of coffee?&lt;/p&gt;  &lt;p&gt;:{&amp;gt;&lt;/p&gt;</description></item><item><title>An Important Consideration for SSIS and SQL Server 2012 Business Intelligence Edition</title><link>http://sqlblog.com/blogs/andy_leonard/archive/2012/04/18/an-important-consideration-for-ssis-and-sql-server-2012-business-intelligence-edition.aspx</link><pubDate>Wed, 18 Apr 2012 11:00:00 GMT</pubDate><guid isPermaLink="false">21093a07-8b3d-42db-8cbf-3350fcbf5496:42854</guid><dc:creator>andyleonard</dc:creator><description>&lt;p&gt;I saw some recent email about SSIS and SQL Server 2012 Business Intelligence Edition. I thought I would share what I have learned.&lt;/p&gt;  &lt;p&gt;It is very easy to misinterpret what one sees in SQL Server Data Tools (SSDT – the new BIDS). When you open SSDT all SSIS components are available, whether or not those components are allowed in your edition of SQL Server. In addition, SSDT will allow you to use &lt;em&gt;and execute&lt;/em&gt; these components in the SSDT Environment at design time. &lt;/p&gt;  &lt;p&gt;&lt;strong&gt;SSIS 2012 BI Edition is &lt;em&gt;Not&lt;/em&gt; SSIS 2012 Enterprise&lt;/strong&gt;&lt;/p&gt;  &lt;p&gt;You can build and test an SSIS package using Enterprise-Edition-only components, but you cannot execute this package outside the SSDT environment. Here’s a screenshot of a BI Edition toolbox:&lt;/p&gt;  &lt;p&gt;&lt;a href="http://sqlblog.com/blogs/andy_leonard/SSISToolbox_075CA020.jpg"&gt;&lt;img style="background-image:none;border-bottom:0px;border-left:0px;padding-left:0px;padding-right:0px;display:inline;border-top:0px;border-right:0px;padding-top:0px;" title="SSISToolbox" border="0" alt="SSISToolbox" src="http://sqlblog.com/blogs/andy_leonard/SSISToolbox_thumb_387BDAC0.jpg" width="152" height="244" /&gt;&lt;/a&gt;&lt;/p&gt;  &lt;p&gt;Note the Enterprise Edition-only components: Fuzzy Grouping, Fuzzy Lookup, etc.&amp;#160; Take a look at what happens when I execute a Data Flow Task that contains a Fuzzy Lookup Transformation in BI Edition:&lt;/p&gt;  &lt;p&gt;&lt;a href="http://sqlblog.com/blogs/andy_leonard/FuzzyExecutionInSSDT_BIEdition_70BA51D8.jpg"&gt;&lt;img style="background-image:none;border-bottom:0px;border-left:0px;padding-left:0px;padding-right:0px;display:inline;border-top:0px;border-right:0px;padding-top:0px;" title="FuzzyExecutionInSSDT_BIEdition" border="0" alt="FuzzyExecutionInSSDT_BIEdition" src="http://sqlblog.com/blogs/andy_leonard/FuzzyExecutionInSSDT_BIEdition_thumb_6B6B6B27.jpg" width="215" height="244" /&gt;&lt;/a&gt;&lt;/p&gt;  &lt;p&gt;Now take a look at what happens when I execute that same package using DtExec on the same virtual machine:&lt;/p&gt;  &lt;p&gt;&lt;a href="http://sqlblog.com/blogs/andy_leonard/ErrorWhenExecutedWithDTExec_75BC8F87.jpg"&gt;&lt;img style="background-image:none;border-bottom:0px;border-left:0px;padding-left:0px;padding-right:0px;display:inline;border-top:0px;border-right:0px;padding-top:0px;" title="ErrorWhenExecutedWithDTExec" border="0" alt="ErrorWhenExecutedWithDTExec" src="http://sqlblog.com/blogs/andy_leonard/ErrorWhenExecutedWithDTExec_thumb_1AD9D9F4.jpg" width="244" height="117" /&gt;&lt;/a&gt;&lt;/p&gt;  &lt;p&gt;Ugliness. And confusion.&lt;/p&gt;  &lt;p&gt;Andy&lt;/p&gt;</description></item></channel></rss>