1. Make Your PACKAGES Communicate BETTER
SSIS 2016
Make Your PACKAGES Communicate BETTER

2. Victor Ivantsov Senior SQl Server developer, 23 years of Experience
TSQL, SSIS, SSRS
MEMBER OF JSSUG, TOASTMASTERS
ENJOY OUTDOOR SOCCER, classical AND ROCK MUSIC
Platelets/plasma DONOR

3. ETL CHALLENGE
ACCEPT ANY FILE TYPE OR LAYOUT FROM YOUR CLIENTS AND LOAD THIS INTO YOU SYSTEM
DEPLOY AND RUN EXACT SAME PACKAGE IN ANY ENVIRONMENT (PROD/STAGE/UAT/QA/DEV/LOCAL)
REUSE CODE and manage upgrades smoothly

4. Traditional PACKAGE CONFIGURATIONS
XML FILE
PARENT PACKAGE VARIABLE
ENVIRONMENTAL VARIABLE
REGISTRY ENTRY
DATABASE TABLE

5. NEW Configuration
CHILD VARIABLE SETTING PARENT VALUE (available IN SQL 2008R2 Edition)
PACKAGE PARAMETERS (AVAILABLE in SQL 2012 edition)

6. HYBRID SOLUTION
BUNDLE Packages TOGETHER, BUT MAINTAIN THE EXECUTION ORDER
FORCE EACH CHILD PACKAGE TO OBTAIN RUN-TIME VALUES FOR THE ENVIRONMENT

7. MASTER LOAD TABLE SCHEMA

8. Integration Sample Data

9. MASTER LOAD PACKAGE

10. NO PARAMERS BINDING

11. LOCAL VARIABLES INSTEAD

12. MASTER LOAD CONFIGURATION

13. MASTER LOAD SUMMARY For a given integration Solution TABLE ROW:
1. pull a list of Packages in Required execution order
2. For Each package – load Required configuration values depending on the environment and STORE THOSE VALUE in Local master load variables
3. execute child package
4. Each child package is forced to retrieve configuration from the parent package.

14. First Child Package - overview

15. First CHILD package - Configuration

16. FIRST CHILD PACKAGE – CONVERSION DATA FLOW

17. COMPILE AND CALL validation DLL

18. VALIDATION WORK FLOW

19. Setting PARENT PACKAGE VARIABLE, FROM CHILD

20. Inside the script task

21. Typical STANDARD package

22. Calling a child package BY PROJECT REFERENCE

23. TAKE AWAY
TOTALLY “INDEPENDENT” PACKAGES CAN PULL AND SET EACH OTHER VARIABLE VALUES
SHARED SCRIPT TASK CODE CAN BE COMPLIED INTO DLL AND REFERENCES (NO GAC!)
ALL PACKAGES DEVELOP/DEBUG LOCALY and DEPLOYED with “DESIGN TIME” VALUES
ONLY CLIENT SPECIFIC or STANDARD DATA FLOWS are UNIQUE
UPGRADES ARE EASY – CLONE AND INCREMENT THE NUMBER

24. Q & A