Success Story Dillinger

DERIVING BUSINESS KEYS All tables and objects feature unique, database generated IDs as primary keys and reference numbers that are known within the department. For the latter, the number ranges are so limited that they are often reused by the business over time. This presents a challenge as a business key in Data Vault should uniquely identify only one business object over time. Therefore, deriving unique keys from the reference numbers or combinations was not possible. Dillinger spent a considerable amount of time analyzing possible business keys based on the reference numbers. The DWH team worked with the departments as well as with colleagues from IT and tried to find suitable business keys for the business objects in the rolling mill. Together with Scalefree’s experience, the result was rather simple: Dillinger had to fall back on the surrogate keys to be used in Data Vault hubs. This sounds a bit unspectacular at first but in practice it was the best decision to be made in this specific case. Most of the objects in the rolling mill exist only in this system or their surrogate keys were also used in adjacent systems making integration very easy. Alexander Brunner, a Scalefree Partner commented: “At the beginning of a project considerable effort should always be taken to identify business keys, because it is worth it. But it is not unusual to fall back on the surrogate key, especially, when the business key candidate is not unique over time which happens sometimes for older source systems, and in addition, it cannot be extended in the same manner over all source systems used, for example by a creation date. In the case of Dillinger, the surrogate key is even used by adjacent source systems, so it is a very good key for the hub’s purpose of integration.”

IMPLEMENTATION CHALLENGES

With Wherescape 3D and RED, Dillinger hoped for a one-button-solution. They were ready to hit that button only to realize that unfortunately it is not that simple. The combination of the two becomes very powerful and enables fully automated, traceable, fast development of ETL routes. The tools are highly customizable which makes them very flexible but some training is needed to effectively use these tools. Also, due to high demand on the market, Dillinger could only get less experts than we would have liked to at the beginning of the project. On top of that, PostgreSQL, as a target, was still very new and some of the features Dillinger needed for Data Vault building were not yet fully available. But this was solved over the course of the first sprints by the excellent project support from WhereScape on- site consulting together with Scalefree.

Made of Steel - Data Vault 2.0 at Dillinger | Scalefree International GmbH

7/13

Powered by