Optimizing Denodo views

When using Denodo for data virtualization and integration, you may be able to improve the performance of Denodo views. For potential options, see below.

Caching

In Denodo at IU, caching is not performed at the server level. Instead, each virtual database (VDB) is configured with an exclusive Oracle tablespace for caching. Developers have sufficient permissions to manage partial caching at the view level.

If you want to use full caching, contact EDSS to request access to the Denodo scheduler. To learn more about caching, see the Denodo Agile performance tutorial.

Examining data lineage

You can examine your data lineage for a derived view by using Tree View. If you are combining data that you don't need, consider redesigning your derived view.

Changing the execution plan

You can change how Denodo executes complex joins by modifying the execution plan. For details, see the Denodo Virtual DataPort Administration Guide. To learn how to view and modify the execution plan, see Editing the Execution Plan. If you wish to try data movement, your cache tablespace is exclusive to your VDB and available for your use.

This is document ajne in the Knowledge Base.
Last modified on 2017-12-08 11:27:41.

Contact us

For help or to comment, email the UITS Support Center.