Great Introductory session by Peter Saddow on Integration Services in SQL Server code-names “Denali”. I have tried to highlight the key learning from this session. Download slides here
SSIS contains new UI improvements for increased developer productivity. It contains new features aimed towards improved deployment, configuration and management of SSIS projects. Everything you had in SSIS 2008 will continue to work; upgrade process should be relatively seamless – Denali comes with a Migration Wizard. DTS 2000 and ActiveX scripts now retired in Denali.
Build SSIS Packages now in Visual Studio 2010
- rounded corners
- improved annotations
- undo-redo supported
- new getting started window
New toolbox and variable buttons for better performance (for enhanced developer experience):
Apply Expressions in Connection Manager and Variables:
Work Offline option for Connection Manager:
Easy to change Variable Scope. By default, a variable scope is set to the package.
Copy & Paste now more intelligent: if you copy and paste an object, it now copies over its dependents.
Upgraded VSTA 3.0 engine under Visual Studio 2010 shell: VSTA 3.0 support .NET 4.0 (C# and VB.NET)
Data Flow Improvements: Flexible Order of Authoring makes it possible to develop a package backwards from the destination.
New Facebook connectors:
New Column Mapper: Automaps by name, ability to filter, export & import mappings to/from excel
Add new data source automatically picks only installed data providers:
New Data Quality Service Cleansing Transform:
Parameters are replacement for configuration: these are read-only variables.
Parameters can be defined as Sensitive and/or Required.
Projects: Combines all packages into a single deployable ISPAC file.
Legacy file based deployment models can be converted to Project based deployment model with the help of a built-in wizard.
New Environment configuration lets you run the package under a specific environment under SSMS.
New Dashboard to show complete status of the package in one place when the package is run on the Server. By default all events are logged on the server.
You can choose to run the package under 64-bit or 32-bit.
Data Tap: You can output the data flowing at any path in a text file (csv format) for later investigation using plain SQL.