Monday, April 20, 2015

SQL Server 2012 SSIS Enhancements



 SQL Server 2012 Undo and Redo Features

For a package, undo /redo is available in the Control Flow, Data Flow, Event Handlers, and Parameters tabs, and in the Variables window. For a project, undo/redo is available for the project parameters.
You can’t undo/redo changes to the new SSIS Toolbox, and you can’t undo/redo shared connections.
To undo an action, click the undo button or press CTRL+Z. To redo an action, click the redo button or press CTRL + Y.




SQL Server Integration Services Toolbox Enhancements
 

In 2012, components inside the toolbox have been placed in few more categories (Favorites and Common) for ease of use.  These categories are not fixed and you can customize it as per your need. For example, you can place all your frequently used components inside "Favorites" section which appears at the top of the Toolbox as shown below:

 


To move a component to some other location/category, right click on the component and click on the location where you want that component to be placed as shown below. 
SQL Server Integration Services Solution Explorer Enhancements
SQL Server 2012 now supports a new project deployment model as well as the legacy deployment model. The Legacy Deployment Model lets you deploy each individual package separately whereas the new Project Deployment Model lets you create deployment packet (which is an *.ispac file) from the SSIS project. Each SSIS project which you create in SQL Server 2012, by default gets created in Project Deployment Model which you can change if needed as shown below:
 


By default, new SSIS projects get created in the Project Deployment Model. When we right click on the project we now have two more options. The "Project Parameters" let's you define the parameters in the project and the "Deploy" option let's you create the deployment package or deploy to the Integration Services Catalog database.
 

If you right click on the package in the Solution Explorer, you will notice one more option (Entry-Point Package). This option is helpful in the scenario when you have a parent package which calls child packages. You can set the Entry-Point Package option for the parent package.