in several projects i have seen the usage of an ODS. Although common in the field of datawarehousing it appears to have different aspects within different projects. Also the place in the architectures sometimes looks strange (for example i’ve seen the ODS inbetween a staging and datawarehouse layer instead of having it besides the staging or datawarehouse area)
In the last few years I have seen a dozen of data warehouse projects. more than 70% were build upon the (Kimball) Bus architecture having a 2-tier layer. Most of the time build “out of the book”. With other words the architecture has not been applied to what the business needs, but how it is common to do in the field of datawarehousing. Read more…
Nobody ever say so, but for so many years now I have been confronted with DWH spaghetti projects. No matter the tools used, somehow it seems an utopia to create a clear architecture / ETL / Datamodel in time.
The problems are huge. People come and go. Without a clear view of what new people have to do they start their own way with their own vision and methods. The beginning of the end. And where does it end? High and rising maintenance cost, disappointed users etc etc. Read more…
It is such a pity that so many designers and -even worse- architects of data warehouses use only 1 architect design for all their customers. It is not called designing under architecture. There is no “one-size-fits-all” architecture for data warehouses. I can image that people still do so because of simplicity in for example implementation. That way even a non data warehouse consultant can implement a data warehouse. It however most often results in poor solutions or failed programs.