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 tables permissions, is that temporary tables are only valid for the same connection, and Data Movement makes use of multiple connections, so we can not rely on the temporary table mechanism.
What if you need to Write back capabilities to data sources connection?
If you had a use case where users would need to write back to the SQL Server database via Denodo, the Insert/Update permissions would need to be added to the list above.
Here s another useful reference, which came from a customer question. This customer was trying to create a denodo 7.0 VDP database, which denodo Virtual DataPort (VDP) would not except and was wondering why. After a little research, it turned out to be VDP database name was a denodo reserved word. While I did find the name finding the Denodo Reserved words for Virtual Query Language (VQL) were incorporated in the text of page which did not immediately return when performing Google Search for “denodo reserved words.” Rather, the ‘List of Reserved Words’ for Denodo Virtual Query Language (VQL) was buried at the end of the Denodo VQL Syntax Conventions.
So, I thought I would pull the list of reserved words into a separate page and post the list of denodo VQL reserved words in this site for the next time some asks me for the list of Denodo Virtual Query Language (VQL) reserved words.
Denodo List Of Reserved VQL Words
CURRENT_DATE | CURRENT_TIMESTAMP
Denodo Related References
Denodo Virtual Query Language (VQL) Syntax Conventions > Denodo Reserved Words
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.
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.
Import 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:
Permissions grants include connection, creation, read, write and admin privileges over a VDP database.
Permissions grants include read, write, insert, update and delete privileges over a view.
VDP Columns Within a VDP View
Permissions grants include the denial of the projection specific columns /fields within a view.
Row Level Security
Row Level restrictions can be added to allow users to obtain only the rows that match a certain condition or to return all the rows masking the sensitive fields
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 input data source and will be the least business friend in their organization, naming, and metadata.
The Semantics layer
The semantics layer is where the major data reorganization, data transformation, and the application of business friend field names and metadata begins. The semantics layer is what folks with a traditional data warehousing background would think of as the Data Warehouse (DW) or Enterprise Data Warehouse (EDW). The semantics layer of the logical data warehouse (LDW) performs serval tasks:
Data from multiple input sources are consolidated
The model becomes multi-dimensional (Fact and Dimension oriented)
Field names and descriptive metadata are changed to meaningful, domain normalized, business-friendly names and descriptions.
Domain normalizing business rules and transformations are applied.
Serves as a data source for the business layer and reporting layer.
The Business Layer
The business layer, which is considered optional by denodo, is modeled along a more narrow business subject orientation and more specialized business rules are applied. This is what folks with a traditional data warehousing background would think of as a Datamart (DM).
The business layer of the logical data warehouse (LDW) performs serval tasks:
Limits and optimizes the data to facilitate business intelligence and report activities concerning a specific line of business or business topic (e.g. Financials, Human Resources, Inventory, Asset management, etc. )
Business-specific/customized rules and metadata are applied
Supplements the semantic layer and serves as a data source for the reporting layer.
Additional data consolidation and data structure denormalization (flattening) may occur in the business layer
The Reporting Layer
The reporting layer, which is considered optional by denodo, is the most customized layer and sees the most reporting topic specialization and specific need transformation. The reporting layer is where a traditional data warehousing may provide customized reporting, or system interface views, interface ETL’s to produce interface files, and reporting team do more of their own development.
The reporting layer of the logical data warehouse (LDW) performs serval tasks:
Provides consumer-specific customized rules and metadata
Provides consumer-specific data organization/layouts
Data is optimized for consumer purposes and may be highly or entirely denormalized to meet consumer needs.
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 Data Warehouse (LDW). To provide some guidance to facilitate the usefulness and performance of base views here are some best practices:
Use consistent Object Naming conventions. It is strongly recommended that the denodo standard naming conventions be used.
Create indexes on Primary Keys (PK), Surrogate keys, and Foreign Keys (FK)
Import and or create the Primary Keys (PK), Foreign Keys (FK), and Associations.
Have Statistics Collection been set and include all critical fields?
Base views, as a rule, should not be cached unless absolutely necessary for reasons of performance.
Create performance Indexes to mirror sources system to improve performance.
Populate view Metadata properties describing the type and the nature of the data which the view contains.
Populate field Metadata properties describing Field. This is important for a few reasons:
The description can be inherited by view built from the base view.
This populates the Denodo Metadata Catalog within which data Stewards can maintain and improve the description.
Informs other developers and user of what the field is/means.
Field metadata should be annotated with “Not Used”, if the field is always null, blank, or empty. This saves time and labor when researching data issues
Retain the original table name (applying naming convention prefix and field names to facilitate data Lineage traceability.?
Use denodo tools against tables, where possible, rather than (Manual) SQL views, Database views, or Stored Procedure. Denodo cannot rewrite or optimize these objects.
A generalizing specialist is simply someone who is multi-skilled. Such an individual can be a specialist in one or more technical disciplines while at the same time actively seeks to expand their skill set, which spans across different areas besides their present specialties. Generalizing specialists are also referred to as cross-functional developers, multi-disciplinary developers, and versatilists.
While they can become more skilled with time, don’t mistake them to be super skilled in every discipline. However, their technical knowledge and general software development knowledge, as well as a good understanding of their relevant business domains, can be critical to getting things done in real-time. The person can easily be redeployed based on the changes in business strategy or other necessary requirements to remain competitive.
Benefits being a generalizing specialist
We live in a fast-changing industry, where being a specialist in just a single discipline alone may not cut it in the larger scheme of things. Since generalizing specialists have knowledge on a broad range of issues, they can see the bigger picture and help make better decisions for greater productivity. As such, the available job opportunities will likely be more compared to specialists. Better yet, you will be able to attract better job offers.
Importance of generalizing specialists
Generalizing specialists are essential to developing high-performing agile teams in companies, and here are some of the reasons they are considered the key to success.
• Better collaboration
While a company will have different departments, they will be connected with others and geared towards accomplishing the same end goal. Communication and collaboration within the teams involved are important elements to achieving that goal, and this is something most specialists aren’t good at. When you don’t have a good understanding of how everything fits together, it’s very easy to look down on what your teammates are doing. Working together effectively might prove a challenging task.
Generalizing specialists are more likely to appreciate the work of others simply because they have a good grasp of different technical and domain disciplines. Their background allows them to understand the issues teammates are trying to find solutions to.
• Improved flexibility
The IT industry, by its very nature, faces significant changes that serious businesses must comply with to remain relevant. With a generalizing specialist, dynamic transition and allocation of the new tasks wouldn’t be a huge problem. Things would look quite different if a team is built of specialists that are just accustomed to doing the same type of tasks over and over again. In fact, this is considered to be risky, as it can result in productivity loss.
• Increased efficiency
Generalizing specialists bring less dependency, which can go a long way in increasing efficiency and productivity. The problem when working with specialists is that they can easily become bottlenecks, especially when they have a lot on their plate. There’s a good chance that multiple development teams will be looking up to the specialist, and this can negatively affect the overall team efficiency.
Generalizing specialists are surely taking over. There’s room for some specialists within IT departments, but as things look at the moment, more departments are moving towards becoming more agile. It’s not unlikely to see only a few specialists survive in the information technology industry over time.