Testing SSIS Packages

Testing SSIS Packages

Brought to you by: PASS DW/BI VC and Tim Mitchell, Microsoft Data Storage MVP

Senior developer: “How do you test your code?” Junior developer: “I compile it.” It’s an old joke, but too often this reflects the reality of testing. If the code compiles, it has passed its test. Sadly, this principle is sometimes applied to Extract-Transform-Load (ETL) processes as well: “When the SSIS package runs without error, testing is complete.”

As in software development, testing of SQL Server Integration Services (SSIS) packages should not end at when the package executes successfully. You must also confirm that the package does what it was intended to do without placing an undue performance burden on the system.

This session walks through design patterns for testing SSIS packages during and after the development process. The session covers topics such as these:

* Performance testing
* Patterns for validating execution results at runtime
* Validating package metadata before execution
* Design time versus runtime testing
* Making a graceful exit: testing for error handling

RSVPURL: https://attendee.gotowebinar.com/register/6092452585517835523

When

iCal
UTC : Wed, Apr 19 2017 16:0017:00
Event Time : Wed, Apr 19 2017 12:0013:00 Eastern Daylight Time
Your Local Time: 4/19/2017 11:0012:00