Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Biml for Beginners: Speed up your SSIS development (SQLSaturday Iceland)

4,308 views

Published on

Biml for Beginners: Speed up your SSIS development (Presented at SQLSaturday Iceland in Reykjavik on June 18th 2016)

Published in: Data & Analytics
  • Be the first to comment

Biml for Beginners: Speed up your SSIS development (SQLSaturday Iceland)

  1. 1. Biml for Beginners: Speed up your SSIS development Cathrine Wilhelmsen · SQLSaturday Iceland · June 18th 2016
  2. 2. Thank you to our sponsors! SQL SATURDAY | #516 | REYKJAVIK 2016
  3. 3. Session Description SSIS is a powerful tool for extracting, transforming and loading data, but creating and maintaining a large number of SSIS packages can be both tedious and time-consuming. Even if you use templates and follow best practices you often have to repeat the same steps over and over and over again. Handling metadata and schema changes is a manual process, and there are no easy ways to implement new requirements in multiple packages at the same time. It is time to bring the Don't Repeat Yourself (DRY) software engineering principle to SSIS projects. First learn how to use Biml and BimlScript to generate SSIS packages from database metadata and implement changes in all packages with just a few clicks. Then take the DRY principle one step further and learn how to update all packages in multiple projects by separating and reusing common code. Speed up your SSIS development by using Biml and BimlScript, and see how you can complete in a day what once took more than a week!
  4. 4. Biml Basics Tools & Projects Code Management …the next 60 minutes…
  5. 5. Cathrine Wilhelmsen @cathrinew cathrinew.net Data Warehouse Architect Business Intelligence Developer
  6. 6. You… …? SSIS developer Easily bored Tired of repetitive work
  7. 7. Work… …? Long development time Many SSIS packages Frequent requirement changes
  8. 8. job done! new standards ...yay Ever experienced this?
  9. 9. Ready for a change?
  10. 10. What is Biml? Business Intelligence Markup Language Easy to read and write XML language Describes business intelligence objects: • Databases, Schemas, Tables, Views, Columns • SSIS Packages • SSAS Cubes
  11. 11. Why use Biml? SSIS: Plumbing Biml: Business Logic
  12. 12. SSIS: Plumbing Time wasted on dragging, dropping, connecting, aligning Create the same package over and over and over again with just a few changes Standards, patterns and templates must be defined up-front Changes must be done in every single package High risk of manual errors More packages, more time
  13. 13. Biml: Business Logic Spend time on what is unique in a package Create a pattern once and reuse for all similar packages Handle scope and requirement changes quickly and easily Changes can be applied to all packages at once Lower risk of manual errors Longer time to start, but then reuse and scale
  14. 14. Will Biml solve all your challenges? Probably not... Biml is a tool for generating SSIS packages Biml is not a pre-defined ETL framework Biml is not a tool for automated deployment ...but it will solve many challenges!
  15. 15. How can Biml help you? Biml is great for large projects with common patterns… Timesaving: Many SSIS packages from one Biml file Reusable: Write once and run on any platform Flexible: Start simple, expand as you learn …but is also useful for smaller projects!
  16. 16. What do you need?
  17. 17. BIDS Helper Free open-source add-in for Visual Studio 60+ features for SSIS, SSAS and SSRS Includes basic Biml package generator bidshelper.codeplex.com
  18. 18. …or you can use the new Biml tools
  19. 19. BimlExpress Free add-in for Visual Studio Code editor with syntax highlighting and Biml Intellisense More frequent updates than BIDS Helper varigence.com/bimlexpress
  20. 20. BimlOnline Free browser-based Biml editor Code editor with Biml and C# Intellisense Reverse-engineer from SSIS to Biml bimlonline.com
  21. 21. BimlStudio Licensed full-featured development environment for Biml Visual designer and metadata modeling Full-stack automation and transformers varigence.com/bimlstudio
  22. 22. How does it work? …generated packages look exactly like manually created packages
  23. 23. Biml syntax <Biml xmlns="http://schemas.varigence.com/biml.xsd"> <Packages> <Package Name="EmptyPackage1"></Package> <Package Name="EmptyPackage2"/> </Packages> </Biml>
  24. 24. Biml syntax: Root Element <Biml xmlns="http://schemas.varigence.com/biml.xsd"> <Packages> <Package Name="EmptyPackage1"></Package> <Package Name="EmptyPackage2"/> </Packages> </Biml>
  25. 25. Biml syntax: Collections of Root Elements <Biml xmlns="http://schemas.varigence.com/biml.xsd"> <Packages> <Package Name="EmptyPackage1"></Package> <Package Name="EmptyPackage2"/> </Packages> </Biml>
  26. 26. Biml syntax: Elements <Biml xmlns="http://schemas.varigence.com/biml.xsd"> <Packages> <Package Name="EmptyPackage1"></Package> <Package Name="EmptyPackage2"/> </Packages> </Biml>
  27. 27. Biml syntax: Attributes <Biml xmlns="http://schemas.varigence.com/biml.xsd"> <Packages> <Package Name="EmptyPackage1"></Package> <Package Name="EmptyPackage2"/> </Packages> </Biml>
  28. 28. Biml syntax: Full vs. Shorthand Syntax <Biml xmlns="http://schemas.varigence.com/biml.xsd"> <Packages> <Package Name="EmptyPackage1"></Package> <Package Name="EmptyPackage2"/> </Packages> </Biml>
  29. 29. Let's generate some packages!
  30. 30. Goal: Load from source to staging
  31. 31. Add New Biml File from BimlExpress menu…
  32. 32. …or right-click on SSIS project to Add New Biml File
  33. 33. Biml files are placed under Miscellaneous
  34. 34. Check Biml For Errors from BimlExpress menu…
  35. 35. …or right-click on file to Check Biml For Errors
  36. 36. Generate SSIS Packages from BimlExpress menu…
  37. 37. …or right-click on file to Generate SSIS Packages
  38. 38. From Biml to SSIS: Control Flow <Package Name="TruncateLoad" ConstraintMode="Linear"> <Tasks> <ExecuteSQL Name="Truncate Table" ConnectionName="Staging"> <DirectInput>TRUNCATE TABLE DestinationTable</DirectInput> </ExecuteSQL> <Dataflow Name="Load Table"> <Transformations>...</Transformations> </Dataflow> </Tasks> </Package>
  39. 39. From Biml to SSIS: Data Flow <Transformations> <OleDbSource Name="Source" ConnectionName="AW2014"> <ExternalTableInput Table="SourceTable" /> </OleDbSource> <DerivedColumns Name="Add LoadDate"> <Columns> <Column Name="LoadDate" DataType="DateTime"> @[System::StartTime] </Column> </Columns> </DerivedColumns> <OleDbDestination Name="Destination" ConnectionName="Staging"> <ExternalTableOutput Table="DestinationTable" /> </OleDbDestination> </Transformations>
  40. 40. .biml vs .dtsx: human-readable vs ALL THE CODE! (20% zoom)(150% zoom)
  41. 41. Ok, so we can go from Biml to SSIS…
  42. 42. …can we go from SSIS to Biml?
  43. 43. Yes! 
  44. 44. Let's reverse-engineer some packages!
  45. 45. Package Importer in BimlOnline
  46. 46. Choose a File
  47. 47. Convert from SSIS to Biml
  48. 48. Choose and filter assets
  49. 49. Copy the Biml…
  50. 50. …or Create /Add to BimlOnline Project
  51. 51. The magic is in the
  52. 52. What is BimlScript? Extend Biml with C# or VB code blocks Import database structure and metadata Loop over tables and columns Expressions replace static values Allows you to generate, control and manipulate Biml code
  53. 53. BimlScript Code Nuggets <# … #> Control Nuggets (Control logic) <#= … #> Text Nuggets (Returns string) <#@ … #> Directives (Compiler instructions) <#+ … #> Class Nuggets (Create C# classes)
  54. 54. BimlScript Syntax <Biml xmlns="http://schemas.varigence.com/biml.xsd"> <Packages> <# foreach (var table in RootNode.Tables) { #> <Package Name="Load_<#=table.Name#>"></Package> <# } #> </Packages> </Biml>
  55. 55. BimlScript Syntax: Control Nuggets <Biml xmlns="http://schemas.varigence.com/biml.xsd"> <Packages> <# foreach (var table in RootNode.Tables) { #> <Package Name="Load_<#=table.Name#>"></Package> <# } #> </Packages> </Biml>
  56. 56. BimlScript Syntax: Text Nuggets <Biml xmlns="http://schemas.varigence.com/biml.xsd"> <Packages> <# foreach (var table in RootNode.Tables) { #> <Package Name="Load_<#=table.Name#>"></Package> <# } #> </Packages> </Biml>
  57. 57. How does it work?
  58. 58. Yes, but how does it work?
  59. 59. Yes, but how does it actually work? <Biml xmlns="http://schemas.varigence.com/biml.xsd"> <Packages> <# foreach (var table in RootNode.Tables) { #> <Package Name="Load<#=table.Name#>"></Package> <# } #> </Packages> </Biml> <Biml xmlns="http://schemas.varigence.com/biml.xsd"> <Packages> <Package Name="LoadCustomer"></Package> <Package Name="LoadProduct"></Package> <Package Name="LoadSales"></Package> </Packages> </Biml>
  60. 60. Biml vs. BimlScript Generate, control and manipulate Biml with C# Flat XML "Just text"
  61. 61. Let's generate a lot of packages!
  62. 62. It's like magic!
  63. 63. Code Management
  64. 64. Don't Repeat Yourself Move common code to separate files Centralize and reuse in many projects Update code once for all projects 1. Include files 2. CallBimlScript with parameters 3. Tiered Biml files
  65. 65. BimlExpress vs. BimlOnline / BimlStudio "Black Box" Only SSIS packages visible Visual Editors All in-memory objects visible
  66. 66. Include Files Include common code in multiple files and projects Can include many file types: .biml .txt .sql .cs Use the include directive <#@ include file="CommonCode.biml" #> The directive will be replaced by the included file Works like an automated Copy & Paste
  67. 67. Include Files
  68. 68. Include Files
  69. 69. Include Files
  70. 70. CallBimlScript with Parameters Works like a parameterized include (or stored procedure) File to be called (callee) specifies input parameters it accepts <#@ property name="Parameter" type="String" #> File that calls (caller) passes input parameters <#=CallBimlScript("CommonCode.biml", Parameter)#>
  71. 71. CallBimlScript with Parameters
  72. 72. CallBimlScript with Parameters
  73. 73. CallBimlScript with Parameters
  74. 74. CallBimlScript with Parameters
  75. 75. CallBimlScript with Parameters
  76. 76. Tiered Biml Files Split Biml code in multiple files and use the template directive: <#@ template tier="1" #> Compile Biml from lowest to highest tier to: • Solve logical dependencies • Simulate manual workflows For each tier, objects are added to the RootNode Higher tiers can use objects from lower tiers
  77. 77. What is this RootNode? When working with flat Biml, the <Biml> root element contains collections of elements: <Biml> <Connections>...</Connections> <Databases>...</Databases> <Schemas>...</Schemas> <Tables>...</Tables> <Projects>...</Projects> <Packages>...</Packages> </Biml> When working with BimlScript, the RootNode object contains collections of objects:
  78. 78. Inside the Black Box: Tiered Biml Files <#@ template tier="1" #> <Connections>...</Connections> <#@ template tier="2" #> <Packages>...</Packages> <#@ template tier="3" #> <Package>...</Package>
  79. 79. Inside the Black Box: Tiered Biml Files <#@ template tier="1" #> <Connections>...</Connections> <#@ template tier="2" #> <Packages>...</Packages> <#@ template tier="3" #> <Package>...</Package>
  80. 80. Inside the Black Box: Tiered Biml Files <#@ template tier="1" #> <Connections>...</Connections> <#@ template tier="2" #> <Packages>...</Packages> <#@ template tier="3" #> <Package>...</Package>
  81. 81. Inside the Black Box: Tiered Biml Files <#@ template tier="1" #> <Connections>...</Connections> <#@ template tier="2" #> <Packages>...</Packages> <#@ template tier="3" #> <Package>...</Package>
  82. 82. Inside the Black Box: Tiered Biml Files <#@ template tier="1" #> <Connections>...</Connections> <#@ template tier="2" #> <Packages>...</Packages> <#@ template tier="3" #> <Package>...</Package>
  83. 83. Inside the Black Box: Tiered Biml Files <#@ template tier="1" #> <Connections>...</Connections> <#@ template tier="2" #> <Packages>...</Packages> <#@ template tier="3" #> <Package>...</Package>
  84. 84. Inside the Black Box: Tiered Biml Files <#@ template tier="1" #> <Connections>...</Connections> <#@ template tier="2" #> <Packages>...</Packages> <#@ template tier="3" #> <Package>...</Package>
  85. 85. Inside the Black Box: Tiered Biml Files <#@ template tier="1" #> <Connections>...</Connections> <#@ template tier="2" #> <Packages>...</Packages> <#@ template tier="3" #> <Package>...</Package>
  86. 86. Inside the Black Box: Tiered Biml Files <#@ template tier="1" #> <Connections>...</Connections> <#@ template tier="2" #> <Packages>...</Packages> <#@ template tier="3" #> <Package>...</Package>
  87. 87. Inside the Black Box: Tiered Biml Files <#@ template tier="1" #> <Connections>...</Connections> <#@ template tier="2" #> <Packages>...</Packages> <#@ template tier="3" #> <Package>...</Package>
  88. 88. Inside the Black Box: Tiered Biml Files
  89. 89. How do you use Tiered Biml files? 1. Create Biml files with specified tiers 2. Select all the tiered Biml files 3. Right-click and click Generate SSIS Packages 1 2 3
  90. 90. How does this actually work?
  91. 91. Biml Basics Tools & Projects Code Management …the past 60 minutes…
  92. 92. What do you do next? 1. Install BimlExpress 2. Complete lessons on BimlScript.com 3. Identify your SSIS patterns 4. Rewrite one SSIS package to Biml (Boost your learning by reverse-engineering with BimlOnline) 5. Expand with BimlScript 6. Separate and reuse common code 7. ...never look back to the days of drag&drop :)
  93. 93. Get things done Start small Start simple Start with ugly code Keep going Expand Improve Deliver often
  94. 94. Biml on Monday... …BimlBreak the rest of the week 
  95. 95. @cathrinew cathrinew.net linkedin.com/in/cathrinewilhelmsen hi@cathrinew.net slideshare.net/cathrinewilhelmsen Biml resources and references: cathrinew.net/biml

×