Solving Problems in ETL using SSIS Allan Mitchell SQL Server MVP
Why am I here Worked with DTS since the beginning Worked onsite with SSIS before RTM Co-Author on Wrox Professional SSIS Book Run − andwww.SQLDTS.com − I am not Microsoft.
Agenda/Content Slide What is ETL and why would I use it? Microsoft ETL through the Years −Data Transformation Services −SQL Server Integration Services −What makes Microsoft ETL a good choice Demos
What is ETL? Extraction, Transformation and Load Moving data from A B Transform, conform data Most often used in Data Warehouse loads Also used for −Data Synchronisation −Data Replication
Traditional ETL Architecture In this traditional scenario, the integration process simply conforms data and loads the database server The database performs aggregations, sorting and other operations … … but has to contend with competing demands for resources from user queries This solution does not scale to very large volumes of data and multiple, complex aggregations Traditional warehouse loading ELT
Rethinking ETL Architecture Leveraging SQL Server Integration Services
Is it important? Getting ETL right is very Important 70% of a BI project is about the ETL Why? −No matter how good the cube guy, the reporter. −Bad data and they are dead in the water
Microsoft ETL through the years SQL Server 7 – Introduced Data Transformation Services – Drag and Drop paradigm – Easy to use – Freely redistributable – Quick – Forgiving
Microsoft ETL through the years SQL Server 2000 – Enhancements to DTS – Mainly engine based changes – Some things however were painful.
Microsoft ETL through the years SQL Server 2005 – Microsoft listened to years of input – Complete rewrite – Separates control flow and data flow logic – Containers Looping Transactions boundaries Restart Points – Easy to make environment agnostic
Microsoft ETL through the years SQL Server 2008 – Enhances SSIS from SQL Server 2005 – Engine multi threading – Persisted lookups – Better feedback from the engine
Demos
Contact – Live Meetings – Websites – –