Associations And Joins
A coworker recently asked a question as to whether denodo generated joins automatically from source RDBMS database schema. After searching, a few snippets of information became obvious. First, that the subject of inheriting join properties was broader than joins and needed to in modeling associations (joins on demand). Second, that there were some denodo design best practices to be considered to optimize associations.
Does Denodo Automatically Generate Joins From the Source System?
After some research, the short answer is no.
Can Denodo Inherit Accusations From A Logical Model?
The short answer is yes.
Denodo bridges allow models to be passed to and from other modeling tools, it is possible to have the association build automatically, using the top-down approach design approach and importing a model, at the Interface View level, which is the topmost level of the top-down design process.
However, below the Interface view level, associations and or joins are created manually by the developer.
Where Should Associations Be Created?
You don’t necessarily need to define an Association at every level, usually, the best practice is to apply associations at following points:
These best practices should cover the majority scenarios, beyond these guidelines it is best to take an ad-hoc approach to create Associations when you see a specific performance/optimization.
