THE SQL Server Blog Spot on the Web

Welcome to SQLblog.com - The SQL Server blog spot on the web Sign in | |
in Search

Andy Leonard

Andy Leonard is an author and engineer who enjoys building and automating data integration solutions. Andy is co-host of the Data Driven podcast. Andy is no longer updating this blog. His current blog is AndyLeonard.blog.

An Important Consideration for SSIS and SQL Server 2012 Business Intelligence Edition

Published Wednesday, April 18, 2012 8:00 AM by andyleonard

Comment Notification

If you would like to receive an email when updates are made to this post, please register here

Subscribe to this post's comments using RSS

Comments

 

Matt said:

Very clever way to get you to upgrade ... Hey look at these fancy tools .. they WORK .. oh you want to use them? .. no no ..

April 18, 2012 7:18 AM
 

Eric said:

Thats very useful information Andy. Its very possible that considerable time could be spent developing ETL packages that then have to be unpicked. Not good for project managers or the individual coders.

I understand from some of the recent blogs & tips about SSDT, that there is a favourites folder. Are there additional user manageable folders at our disposal?

Is it feasible to create site specific menu templates that suppress those components that aren't permitted for that site?

April 18, 2012 8:09 AM
 

Andrew said:

Similar to the approach with the Developer edition I guess. Although you would have thought this wouldn't propagate to full licensed editions.

Frustrating!

April 18, 2012 9:44 AM
 

Rafi Asraf said:

There should be an option, in the project setting, to define which platform you are developing to, and then the build should fail, when you are using parts which do not qualify.

This issue exists in the analysis services projects in BIDS 2008 and 2005, because you can build a cube, that uses semi additive measure etc, which are not allowed on a standard edition. To solve the problem, the SSAS project in bids have a platform setting, standard or enterprise, and when you pick standard, it will not late you build, if you are using non standard edition features.

I can see that the same solution is also used for SSAS projects, in visual studio 10, aka SSDT, so why they didn't do that for the SSIS projects, that is the big question.

\Rafi

April 18, 2012 10:49 AM

Leave a Comment

(required) 
(required) 
Submit

This Blog

Syndication

News

My Latest Book:

Community Awards



Friend of Red Gate

Contact Me

Archives

Privacy Statement