Tag: Data Virtualization

Technology - When To Cache A Denodo View

Technology – When To Cache A Denodo View

Here’s a quick summary of practices about when to use cache when developing denotative views.  These guidelines come from the usual documentation and practical experience and may help you decide whether to cache a view. These are general guidelines, and they should happen the conflict with any guidance you’ve gotten from the Denodo; Please use the advice provided by Denodo. What is a table cache? In denodo, a cache is a database table that contains a result set of a view at the point in time, which is stored in a JDBC database Why Cache? Cache in Denodo can be

Continue reading

Technology – Denodo Supported Business Intelligence (BI) and Reporting Tools

The question of which PI tools to Denodo supports comes up perhaps more often than it should. The question usually comes in the form of a specific intelligence (BI) and reporting tool being asked about. For example, does Denodo support tableau or Cognos, etc. Denodo does provide a list of intelligence (BI) and reporting tools that they support. However, the list of the most commonly used intelligence (BI) and reporting tools. And there is a reason for that, which, basically, boils down to whether or not the intelligence (BI) and reporting tools can use ODBC or has a JDBC driver. 

Continue reading

Technology – Denodo VQL To Get A List Of Cached View Names

Hello, this is a quick code snippet of a Denodo VQL (Denodo Virtual Query Language) to pull a list of cached view names which can be useful in pulling list of cached views. It’s not a complicated thing, but now that I’ve bothered to look it up on putting this note here mostly for me but you may find useful. I have found this useful for several reasons not the least of which is for creating jobs to do maintenance of cached view statistics. Example VQL List Of Cached View Names select name view_name from get_views()        where cache_status <>

Continue reading

Denodo View Performance Best Practice

Since I have been doing more training of beginning users of the Denodo, there have been a lot of questions around performance best practices and optimization. This article is a quick summary of some of the high points of the Donodo documentation, which are typically useful. However, I would like to point out that the performance of Denodo views is: usually, an ongoing process as your environment evolves and that your code changes also, the performance of Denodo views may involve elements be on the Denodo framework itself, such as source system databases and may require some administration configuration and

Continue reading

List of denodo supported JDBC databases

The question ‘What are the JDBC databases supported by denodo” is one of those questions, which always seems to come up either in customer meetings, Proof Of Concept (POC) implementations, or planning for POC’s. While it is documented by denodo, I seem to spend more time looking for it than I should. So, I thought it might be useful to document the Supported JDBC Data Sources page URL for easy reference. Related References Denodo > User Manuals > Virtual DataPort Administration Guide > Appendix > Supported JDBC Data Sources https://community.denodo.com/docs/html/browse/7.0/vdp/administration/appendix/supported_jdbc_data_sources/supported_jdbc_data_sources

Continue reading

How to save Denodo Virtual Data Port (VDP) VQL Shell results

In a recent project, I was asked by a new user of Denodo Virtual Data Port (VDP) how to save denodo VDP VQL Shell results. So, here is a simple outline of the process of exporting the VQL Shell results: Execute the VQL Shell SQL Click on the ‘Save’ button in the ‘Results’ tab to save the results A dialog box will open Check  ‘include Results’ checkbox Set the separator character Set the path of the Output file and desired filename. If you want to the results with a header in a delimited file, enable ‘Include header’ checkbox. Click ‘OK’

Continue reading
%%footer%%