You can translate the question and the replies:

How to isolate denodo from unexpected source environment updates

Hi, Is there any advice on how to isolate denodo from source environment updates that are unwanted/unexpected cascading into denodo base views? We have implemented our views with the branch pruning approach so cascaded changes should be minimised but we still see updates propogating from source environments. This can happen in dev/qa/prod environments. I was thinking along the lines of technical features we can implement along side formalised internal procedures between environment teams. For example - would there be a benefit in implementing interfaces on both ends of the tree view structure? Thanks for your assistance.
user
16-11-2021 05:27:05 -0500
code

1 Answer

Hi, Could you clarify what you mean by source environment updates cascading into denodo base views? When an underlying data source is modified, the base views won’t update unless you click on the source refresh button. To avoid service interruptions in data sources, I would enable [cache](https://community.denodo.com/docs/html/browse/8.0/en/vdp/administration/cache_module/cache_module) on the views. Hope this helps!
Denodo Team
16-11-2021 16:39:33 -0500
code
You must sign in to add an answer. If you do not have an account, you can register here