Share:

Bartosz Ratajczyk

SQL Server developer, trainer and administrator living near Warsaw, Poland. Currently working as a consultant for 7N. Involved in a data warehouse project, where he builds ETL processing with SSIS. Started with SQL Server over 10 years ago, since version 2000. Fan of automating repeatable tasks, especially with PowerShell. Local user group and conference speaker, active Polish Data Community (former PLSSUG) member. MCSE Data Platform and MCT. When he does not work or attend/present at the conferences he's mostly spending the time at home with wife, daughter and some dogs (four) and cats (eight, and - probably - counting ...)



Presenting

Start testing your SSIS packages with ssisUnit

How do you test your SSIS packages? Do you prepare them, set the parameters and variables, maybe get some sample or production data and run few times by hand in SSDT? It’s not a bad practice when you start your ETL journey, but after some time you probably think about automation. If not – you should. Perhaps you have some SQL scripts that verify data in the tables after package execution, but if you are like me, somewhere inside you feel that it’s not enough. It’s time you start automated SSIS unit and integration testing. On this session, I will show you why you should and how to start with automated testing of the packages and the whole projects using ssisUnit – the free SSIS testing library. I will start with some basics and move forward to the real-life examples of the unit and integration testing of the SSIS packages/ projects/solutions. You will see the benefits of automated testing and that testing is hard only at the beginning.

300