2. Today’s Plan
Project model
New features
SSISDB catalog
Deployment
Configuring & Executing packages
Troubleshooting
Management
4 | 4/14/2012 rafael-salas.com
3. Not Covered In This Session
SSIS Fundamentals
Enhancements not related to project model
Package deployment model
Upgrade & conversion of packages
5 | 4/14/2012 rafael-salas.com
4. Enterprise Information Management
Where Does SSIS Fit?
Integration Services Data Quality Services Master Data Services
• Enterprise Class ETL • Knowledge-driven data • Master Data
cleansing Management
• Robust, Flexible,
Scalable and extensible • Corrects, de-duplicates • Broader reach with new
Architecture and standardizes data Excel-Ad in
• Integrates with • Integrates with Data
Integration Services Quality Services
Complete, Current, Clean and Consistent Data
6 | 4/14/2012 rafael-salas.com
5. SSIS 2012 Server
Centralized
Configurations
Deploy, Execute and Manage
Role-based Security Projects and Packages
SSIS Server
SSISDB SSMS
Managed API
T-SQL
Built-in Operational
Logging & Reporting
Project
Troubleshooting Versioning
Performance and Data
Issues
7 | 4/14/2012 rafael-salas.com
6. Project Deployment Model
Deployment unit is the project (.ispac)
Reference other packages in project
No connection managers needed
Parameters
Package configurations replacement
Project connection managers
VS configurations
Deploys to SSISDB catalog
8 | 4/14/2012 rafael-salas.com
7. Demos
Build Deploy Execute
Create project package
project project
Shared SSIS env. Configure
Parameters conn. & run time
managers variables values
Debug SSIS
Configure data Operationa
dump logging
taps l reports
files* levels
Active Operations Server Properties Project Versioning
9 | 4/14/2012 rafael-salas.com
1,000 foot view of the server, focusing on interactions beween the catalog and the execution process.This diagram shows how ISServerExec interacts with SSISDB. It also shows how object model is used by ISServerExec.There are two communication channels between ISServerExec. Named pipe and an SQL connection. In general, the named pipe is used whenever SQL behaves like a client. The SQL connection is used when ISServerExec is the client. Before starting executing a package, ISServerExec sets up event listener and log providers to receive events and logs from runtime. The events and logs are filtered according to logging level setting and written to SSIS DB through the SQL connection.
