Testing ETL Processes by Gary Sieling.
From the post:
ETL (“extract, transform, load”) come in many shapes, sizes, and product types, and occur under many names – “data migration” projects, business intelligence software, analytics, reporting, scraping, database upgrades, and so on. I’ve collected some notes, attempting to classify these projects by their principal attributes, so that you can estimate the risks and plan the testing process for similar projects- if you have other additions to this list, please add comments below.
…
I count twenty-six (26) distinct risks and there may be others.
Are you in the eternal cycle of ETL?
For data to be improved, it’s ETL time?
There are alternatives.
Such as annotating data in place.
If you have ever seen the graphic of a topic map hovering over an infospace, you know what I am talking about.
(Image by Lars Marius Garshol)
Questions?