Tag: Structured Query Language (SQL)

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

SQL server table Describe (DESC) equivalent

Microsoft SQL Server doesn’t seem have a describe command and usually, folks seem to want to build a stored procedure to get the describe behaviors.  However, this is not always practical based on your permissions. So, the simple SQL below will provide describe like information in a pinch.  You may want to dress it up a bit; but I usually just use it raw, as shown below by adding the table name. Describe T-SQL Equivalent Select *   From INFORMATION_SCHEMA.COLUMNS Where TABLE_NAME = ‘<<TABLENAME>>’; Related References Microsoft SQL Server – Useful links SQL Server – Basic SQL Server Object Naming

Continue reading

Database – What is TCL?

TCL (Transaction Control Language) statements are used to manage the changes made by DML statements. It allows statements to be grouped together into logical transactions. The main TCL commands are: COMMIT SAVEPOINT ROLLBACK SET TRANSACTION Related References Database Table Field Ordering Effective Practices Structured Query Language (SQL) Tuning What is DDL? What is DML? What is DCL?  

Continue reading