Tuesday 14 July 2015

SQL Server : Differences between SSIS 2008 and 2012

SSIS server: SSIS server is no longer a separate service that you connect to, it now appears as a node in Object Explorer when connecting to a SQL Server database instance

SSIS Catalog, which is a database that stores deployed projects, environments, and package execution logs.  Each SSIS server has one catalog.

SSIS Projects -  which is an encapsulation of multiple packages into a single unit that you build, deploy & execute.

SSIS Environments are fairly self-explanatory – they are a wrapper for all environment-specific information (e.g. Connection Strings) that you want to maintain outside of a package and when you execute a package you have to choose which Environment to execute it against. In short Environments are the replacement for SSIS configurations and they work hand-in-hand with Parameters that are also getting introduced in SSIS code-named Denali. 


Data tap: At any path, capture all the data coming through and output it to a text file to review later.  This is done without having to modify the package.


SSIS 2008
SSIS 2012
Undo And Redo
No Undo And Redo feature in SSIS 2008
Undo And Redo feature available in SSIS 2012.
SSIS PARAMETERS
SSIS Parameters at package level
SSIS Parameters at the package level, task level and project level.
DQS TRANSFORMATION
No DQS in SSIS 2008.
DQS Transformation is available in SSIS 2012.
Change Data Capture (CDC)
Introduced in SSIS 2008. But there is no task to support CDC in SSIS 2008.
CDC ControlTask available to support CDC in SSIS 2012.
Data Flow Tap
No Data Tap Available in SSIS 2008.
Data Tap Available in SSIS 2012.
Deployment
Package Level Deployment
Project Level Deployment
Package Level deployment
Logging
Disabled by default
Enabled by default and improved
Newly introduced
-          
SSIS server
SSIS Catalog
SSIS Environments
SSIS Parameters
Shared Connection Managers
Offline Connection Managers
Improved
-          
Column mapper
New Reports included [catalog].[execution_data_statistics] 
 Debug the Script component by setting break points
Execution
runs package locally and uses local components like drivers
When you use the “Run Package” command in SSMS, the package runs on the server,
Version control
-          
Each Package is tracked and can be rolled back

Warm Regards,
Chhavinath Mishra 
Sr. Specialist Database Administrator

No comments:

Post a Comment