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 section 4.8.8; for advice about changing the execution plan, see section 20. 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-03-27 11:50:33.

  • Fill out this form to submit your issue to the UITS Support Center.
  • Please note that you must be affiliated with Indiana University to receive support.
  • All fields are required.

Please provide your IU email address. If you currently have a problem receiving email at your IU account, enter an alternate email address.

  • Fill out this form to submit your comment to the IU Knowledge Base.
  • If you are affiliated with Indiana University and need help with a computing problem, please use the I need help with a computing problem section above, or contact your campus Support Center.

Please provide your IU email address. If you currently have a problem receiving email at your IU account, enter an alternate email address.