i’ve long been writing and advocating the need for dynamic data warehousing, which in my definition inlcudes dynamic structuring of the data set. well, in a batch world this process that adapts structure needs to start with the staging area. while this article from an author on sqlserver is not a fully automated process, it’s close. it is a step in the right direction. this author talks about “dynamically” changing the stage load code based on data-driven table definitions. this is not the first time i’ve seen this, some of my friends built etl generators based on structure, but this is the first time i’ve seen this in ssis, and to have it so fluid that the etl doesn’t need to be re-imported every time the structure changes, now that’s interesting.
the article is a fairly good write-up, and i would encourage you to read through it. i bet that most of you can convert the code to db2 9.1, teradata, or even oracle. would love to see that happen, and see what results you get.
there are several issues left unanswered by this article:
* performance, i have no idea how the performance of this load process pairs up with performance of static structuring, the author doesn’t give any clues there.
* still a manual structure adaptation, the maintenance person still has to check and add the structural changes to the columns in the database that define the tables.
the next step, would be to build a “structural profiler” that can peer in to the file, and detect the structure – and make the structural changes to the database for you… this is where the real fun begins.
none the less, it is an interesting article, i enjoyed it, and i hope you do to.