1 / 23

SSIS Field Notes

SSIS Field Notes. Darren Green Konesans Ltd. My Checklist. Standards Logging Configuration. Common Princiapls. Common design decisions or patterns Logging Frameworks Custom vs Stock. Basic Standards. Solution and Project structure ETL vs ELT Staging Custom components.

ravi
Download Presentation

SSIS Field Notes

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. SSIS Field Notes Darren Green Konesans Ltd

  2. My Checklist • Standards • Logging • Configuration

  3. Common Princiapls • Common design decisions or patterns • Logging • Frameworks • Custom vs Stock

  4. Basic Standards • Solution and Project structure • ETL vs ELT • Staging • Custom components

  5. Source Control • Products • Team Foundation Server • Subversion (Visual SVN) • Others… • Issues • Cannot merge or use standard conflict resolution • BIDS Helper- Smart Diff • TFS, SourceSafe,File • BI Smart Diff • Subversion

  6. Naming Conventions • Prefix notation, e.g. DFT for Data Flow Task • http://consultingblogs.emc.com/jamiethomson/ • Expand Name property • SQL Create Year Staging Table • Expand Description property • Create the year named staging table. Any existing table will be dropped first. • Documentation tools are not clever

  7. Logging • Performance monitoring • Real-time monitoring • Trending to justify upgrades • Re-write problem packages • Upgrade hardware / network / environment • Problem solving • Why did the job fail last night?

  8. Logging Options • Built in SSIS logging • Good for standard stuff, including errors • Maintenance routine to prune records • Delete Info daily, Warnings weekly, Errors monthly • Custom SSIS logging • Log process specific metrics - row counts • Event Handler or Control Flow • Windows Logging • Event Log • Performance Monitor

  9. Prune – Delete in Chunks SET @Count = 1000 WHILE @Count IS NOT NULL AND @Count > 0 BEGIN DELETE TOP (@Count) FROM dbo.sysdtslog90 WHERE StartTime < @MinStartTime SET @Count = @@ROWCOUNT -- Pause for 0.2 seconds WAITFOR DELAY '000:00:00.200' END

  10. Frameworks • Consistent logging approach • Process or package state • Passing state between package processes • Saving state for the next run • Last extract date • Complete run only once per day • Dynamic execution workflow • Managed in tables not Control Flow • Easier to manage logical units and reuse

  11. Frameworks • Standard approach reduces costs • Lower support costs • Higher quality through reuse • Cost of applying and maintaining framework • Maintainable frameworks are key! • Custom components encapsulate code • Use the API to bulk apply changes

  12. Custom Components • Task • Pipeline Component • Source • Destination • Transformation • Log Provider • Connection Manager • For Each Enumerators

  13. Using Custom Components? • Easy to manage and update • Good for re-use • Can add/edit functionality easily • One file per machine for all packages • Good for frameworks or complex operations • Good debugging and testing support • Require .NET development skills • External dependency • Additional step during the initial deployment, but also single update step thereafter

  14. Stock Components & Scripting • Faster to develop • Familiar and easy to understand • Don’t write your own data flow engine in a script component! • Acknowledge the need for reuse when it exists and create a shared external assembly • Self contained - No external dependency • Copy and paste package maintenance • Not good for frameworks or common patterns

  15. Recovery & Restarts • Checkpoints – Native • CheckpointFileName, SaveCheckpoints, FailPackageOnFailure • Task level restart only • Partition your Data Flow • Raw files • Variable values are persisted • Configurations not refreshed • Event handlers within checkpoint scope

  16. Recovery & Restarts • Auto-Recovery – Roll your own • Check with IF EXISTS… • Framework workflow • Table of packages with status • Package or task level restart • Variables and precedence constrains expressions • Delete and re-load • No change tracking or updates

  17. Wake up – a quick demo…

  18. Anti-Pattern #1 • Send Mail Task for Errors • Control Flow or Event Handlers • Exceptions cause multiple events • Use external host to handle exceptions • SQL Agent • Use a report

  19. Anti-Pattern # 2 • Multiple Configuration Types • Use one configuration type • Use indirect or ordered pointer configuration • Easier for support and deployment

  20. Sorting • Why sort? • Merge Join • Ordered Analysis • Running totals • Ranking • Script Component • Custom Component • Rank Transform

  21. Sorting • How to sort? • Sort Transformation • Ordinal Nsort • IvolvaExtraSort (2005) • Sort in Source – ORDER BY

  22. Sorting

  23. Thank you • Questions? • DarrenGreen • darren@konesans.com • www.konesans.com

More Related