Tag: logical data warehouse

Denodo Source Database Permissions For SQL Server

Denodo does not publish a concise list of what permissions denodo needs in a source database.  So, I thought I would document what is required for a SQL Server data source for denodo. Source database Dendo Access Permissions Assuming there is no need to write back to the source DB, the data source connection permissions in a SQL Server the denodo source database should be: Read And View Definitions access Create tables (for data movement optimization), and Access to getSchemas() Why Create Table, Not Just Temporary Table? The reason by denodo needs create tables permissions, rather than just create temporary

Continue reading

What Did The Denodo Read Privilege Change To In Denodo 7.0?

Well, the question was asked today by a customer, what happened to the “Read” denodo user privilege between version 6 and version 7.  So, I had to a little research and thought to write it down here, in case anyone else happens to ask or wants to know. The Denodo 6.0 “Read” privilege is now the “Execute” privilege in version 7. According To The Denodo Documentation: In Denodo 7.0, the privilege “Read” has been renamed to “Execute” to clarify its behavior. In VQL statements, the “READ” token can still be used to keep backward compatibility with existing VQL scripts. The

Continue reading

Technology – Denodo Security Enforcement

As the Virtual DataPort Administration Guide, explains in the section “Types of Access Rights” section, on VDP databases, views, rows, and columns. The denodo role-based access mechanism controls how and what a user or user role can use in the virtual layer, including the data catalog. Important Denodo Security Notes Consumer security authorization is imposed at the object level, then Data Level Consumer security authorization is not imposed on Modeling Layers/VDP Folders Using a virtual database to partition projects or subjects is a Best Practice Basically, the ability to grant security is as follows: VDP Database  Permissions grants include connection,

Continue reading

Denodo Data Consolidation & Denormalization

As the data modeling process in denodo moves through the conceptual layers of the data warehouse, there is an evolution of the data structure and their associated metadata. The Base Layer As the modeling process begins the base layer is the ingestion layer, where the source system data structures are recreated in denodo and field are transformed in denodo Virtual Query Language (VQL) data types. the Business layer is what folks with a traditional data warehousing background would think of as Staging or landing. These base layer views should most closely mirror the technical structure and data characteristics of the

Continue reading

Denodo Best Practices For Base Views

The denodo “Base Layer” in the Logical Data Warehouse (LDW) can be thought of as the Data Staging local layer in a more traditional data warehouse (DW) development pattern.  The Base layer is the level at which the source system data structures are transformed into denodo field types and the source data structures are rendered as created in base views (bv). Base views (bv), the first step in virtualizing data, are the denodo structures reflecting the source system structure and the second step behind the data source connection and, therefore, are essential elements for the other layers of the Logical

Continue reading
%%footer%%