What’s New in SQL Server Integration Services 11 CTP1

November 30, 2010


This is a live post from the session of Eran Sagi at Tech Ed Israel 2010 .

SSIS 11 CTP1 still runs on Visual Studio 2008

An easy and quick zoom on the flow

Custom toolbox:
A special toolbox for SSIS
Grouping by functionality (like before) and by favorites, common
Information on each component and a small help icon which will be online and specific for that component with videos and How To for that component.

A new data source (and destination) wizard to assist you in building the data source more easily.

Each task takes its own Meta Data. We’re no longer dependant in one component by the ones that came before it. We don’t need to reconfigure it if we deleted something before it.
In case of a problem in the Meta Data, we can use mapped columns, whether with auto match or by choosing on our own.

An ability to group components to helps you understand more easily the package visually. (Does not affect the way the components run).

Undo support and redo support

In SSIS 11 CTP1 we have a project as a container for a few packages which we can move parameters between them. We can now have better and easier administration of our packages.
Parameters getting their value from outside and then become unchangeable inside the running of the package. Server name is a string batch number is int32. We no longer necessarily need a configuration file which we should change from the environment of the development to that of the production.
Variables can change during run time. Parameters cannot. A variable can take the value in the parameter (server name) and we can use it in the variable to add something to it (a certain folder in that server). That way we can use the data in a parameter in an expression.
We can define a parameter in the scope of the whole project and not just for the specific package.

The SSIS server – improving the deployment and management for the SSIS packages.

No more need for dependency on the login name and password of the package administrator or the SQL Server Agent. Administration is now through the server.

We can migrate from SSIS older version to newer version and we can also decide if we want to downgrade.

Environments – sets of values that can be supplied to the packages.

Entry point package – a few packages in one project can be the entry point in that project. We have an easy way to identify them and give them the parameters.

Add comment
facebook linkedin twitter email

Leave a Reply

Your email address will not be published.

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <s> <strike> <strong>



  1. Praveen DayanithiDecember 3, 2010 ב 16:13

    Hello Ella,

    Nice quick summary you have got here! Thanks for the info….

    Do you know if SSIS 11 RTM or SSIS 11 CTP2 (if any) versions going to be supported by Visual studio 2010? Just curious!


  2. Ella MaschiachDecember 5, 2010 ב 13:37

    Hi Praveen,

    Glad you enjoyed the post!
    SSIS 11 RTM will definitely be supported by Visual Studio 2010. I’m guessing that so SSIS 11 CTP2 (though that’s just a personal guess). I understood that SSIS 11 CTP1 is in Visual Studio 2008 simply because they were rushing to release it.

    All the best,

  3. KaylaOctober 25, 2012 ב 23:36

    I believe that SSIS has eolevvd to a point where it can handle multiple and complex transformation in memory. ETL packages shall be database agnostic and should minimize the need for adding any special procedure or feature to the source, other than granting proper rights to read it. This makes the packages transportable and easy to migrate from 1 SSIS server to another, as well as easy to let the datasource migrate from one place to another.Now, in certain conditions where the data extracted requires several tables joined, and the output is for several million rows, the sort operation can benefit from the database engine as it is optimized to deal with such a task in the most efficient way.So I agree that it depends. But I tend to have as much as possible on the SSIS side as the database is not designed to perform any transformation in an efficient way. The RDBMs engine is optimize to store and retrieve data and keep it in a very relaible state.