Datometry Documentation

Acts as a logical hypervisor that translates all communication between the applications and database in real time. This means applications continue to function as before—unchanged—while the underlying database is replaced with a modern, cloud-native database.

Datometry products use a communication protocol for all communication between client tools and Hyper-Q. The Datometry protocol is a modern protocol that implements asynchronous communication with low latency. Its design is specifically geared to enable effective communication between on-premises clients and cloud data warehouses.

Hyper-Q also supports the Teradata legacy protocol and enables native tools to communicate directly with Hyper-Q. For improved throughput and latency, however, the use of the Datometry tools and connectors is highly recommended.

A full-featured, high-performance ODBC driver based on DCP. As with all Datometry tools and utilities, the ODBC driver is a drop-in replacement for legacy drivers and offers identical functionality.

SQL language definition of the destination system. For example, T-SQL in Azure Synapse includes proprietary SQL and extensions over and above the SQL standard.

Hyper-Q lets applications originally written for a specific database run natively on a cloud data warehouse. Hyper-Q enables enterprise to replatform to public cloud without a highly time-consuming, costly, and risk-laden database migration.

Metadata Store contains annotations, a type of metadata for name resolution that identifies complex SQL constructs that Hyper-Q emulates. Hyper-Q stores this metadata in a separate schema named __DTM_MDSTORE. The __DTM_MDSTORE schema contains information such as if a column is case sensitive or not, and the date format to use with a given column among many other characteristics of the SQL being emulated. Hyper-Q references this metadata when emulating queries from Oracle or Teradata clients for the use with the cloud-based data warehouse.

Datometry PolyLoad is a powerful high-performance data import/export utility that subsumes the functionality of several Teradata tools. PolyLoad executes import/ export scripts in the format of FastLoad, FastExport, and MultiLoad.

Hyper-Q maps client load operations to the native load mechanisms of the destination data warehouse. PolyLoad transmits data from and to Hyper-Q using one or more connections utilizing maximum bandwidth between client and Hyper-Q.

Datometry PolySQL is a rich query client that offers both interactive and batch processing capabilities. It implements control flow elements that are executed on the client within PolySQL and sends SQL expressions to Hyper-Q. This processing matches the functionality of Basic Teradata Query (BTEQ). Existing BTEQ scripts can processed directly with PolySQL.

qInsight provides a unique and detailed breakdown of all interactions of analytical application with the data warehouse. During the analysis, qInsight parses queries to extract and categorize SQL and database features. The insights provided in the report paint a complete picture of effort and risk associated with a replatforming effort.

qShift transforms the original source schema into a SmartSchema™ on the destination system. SmartSchema™ can represent additional data and object types that do not natively exist on the destination system and optimize for performance and completeness.

Term in either Source or Destination SQL to query the underlying data. May also include data manipulation language (DML). For example: INSERT, DELETE, or UPDATE.

qShift transforms the original source schema into a SmartSchema on the destination system. SmartSchema can represent additional data and object types that do not natively exist on the destination system and optimize for performance and completeness.

SQL language definition of the source system. For example, Teradata SQL. Includes pre-standard and proprietary language extensions.

Any statement submitted by an application as a request to Hyper-Q. Includes data definition language (DDL) to create, drop, or modify database objects, as well as maintenance operations.

Hyper-Q utilizes user defined functions (UDFs) to implement standard functionality. These are referred to as Standard UDFs. The UDFs must be installed in the cloud-based data warehouse instance and updated with each new Hyper-Q release.