Layers of a Logical Data Warehouse in Querona are just views. No need to design ETL processes, it is enough to decide which views are cached, when and where.
Querona self-service interface makes it simple to connect new data sources, explore data and prepare data marts for reports. You can decide what should be cached or stored in EDW later.
A cloud data warehouse may be quickly selected as a caching database. Data loading for a selected view is just one button click. A cloud warehouse is protected by Queronaâ€™s Windows Integrated authentication, access rights, and data masking.
Querona Data Virtualization layer is a single access point to all data sources. Authentication, role-based authorization, multilevel access rights and data masking is enforced on all data sources.
Slow queries may be accelerated using caching, in-memory processing on Apache Spark or query retargeting to a different execution engine. Query rewrite will automatically choose the best preaggregate.
Querona supports multiple SQL execution engines at the same time. You can simply decide which data is cached on which caching database and what is stored in Hadoop.
Experienced business analysts and data scientists may be granted rights to manage their area of the data warehouse. Now a data scientist can perform actions that previously required IT help.