You can translate the question and the replies:

Isolated query of a joint view

Hello, is it possible to solve the following scenario: I have two views with different sources, which I would like to join (a push-down is therefore not possible). I want to join these views and make them available for reporting. However, the reporting now only wants to query one column from this view. Denodo executes this query on the correct source, but still pulls data from the other source to join it. Is it somehow possible to skip this join and actually run this one column without using the other source and without having to build a new view? This would drastically increase my performance at least for this scenario. However, I can also understand that this requirement may not be immediate, hence my question if this could not be switched on somehow. Kind regards
14-04-2021 11:47:21 -0400

1 Answer

Hi, The Denodo engine performs static optimizations such as **Branch pruning, Aggregation Push down**,.. to improve the query performance. However, it is necessary for the optimizer to apply some optimizations only if the view definition has certain constraints. For this scenario, I would define **[associations](** between the join views by which the query optimizer will perform **[Branch pruning](** optimization to prune the delegation to the other data source. For more information on branch pruning optimizations, you can take a look at the **[Associations in Denodo](** and **[Denodo Query Optimizations for the Logical Data Warehouse](** Knowledge Base Articles. Hope this helps!
Denodo Team
16-04-2021 08:35:01 -0400
You must sign in to add an answer. If you do not have an account, you can register here