Alation Analytics V2 Database Model

Alation Cloud Service Applies to Alation Cloud Service instances of Alation

Customer Managed Applies to customer-managed instances of Alation

Applies from version 2020.3

Schema and Tables Explained

The Alation Analytics V2 package includes:

• A data dictionary with descriptions of all tables and recommendations on how to do JOINs.

• Sample queries — to be found in the Description field of the schema Public

• Documentation in the form of Alation articles that explains the Alation Analytics V2 schema and some of the best practices for writing queries:

  • Introduction to Alation Analytics — Article describes tables in Alation Analytics V2 and relationships between them

  • Alation Analytics ERD — Article contains the entity relationship diagram (ERD) of the Alation Analytics V2 database

The data dictionary and the articles are available in Alation after the Alation Analytics V2 database has been initialized and this data source becomes available in the Alation catalog. Use Search to find the articles by their titles.

The qli_events Table

The table qli_events is intended to provide a comprehensive view of data consumption at the data source, query, and user levels. Users need to be aware of these limitations:

• The qli_events table is activated on demand. Please reach out to your account executive or Alation Support for activation. After activation, the data will become available after an ETL run.

• In versions 2024.1.3 to 2024.3.1, the qli_events table was limited to supporting one month of historical data upon activation, capped at 30 million rows. Starting with version 2024.3.2, enhancements to the pipeline have increased the capacity to approximately 120 million records per month, allowing for extracting four times more data than the previous limit for the same duration.

• After activation, the table supports up to 90 days of additional data over the historical data populated at the time of activation.

• Currently, the qli_events data is only in General Availability (GA) for Snowflake data sources. We aim to expand the General Availability to include more data sources in future releases.

Alation Analytics V2 ERD

These images can be opened in a new browser tab for a detailed view (right-click on the image > open in a new tab).

Version 2025.1

Version 2024.3.2

Version 2024.1.3

Version 2024.1.1

Version 2024.1

Version 2023.3.5

Version 2023.3.3

Version 2023.3.2

Version 2023.3.1

Version 2023.3

Version 2023.1.7

Version 2023.1.5

Version 2023.1

Versions 2022.2 to 2022.4

Using Compose

Users with access to the Alation Analytics V2 database can query it in Compose after they connect with their individual account.

See User Access to Alation Analytics V2

Sample Queries to Retrieve Data from Data Quality

Available from version 2025.1

Alation Analytics v2 (AAv2) supports the inclusion of data quality or health data for reporting purposes.

With this integration, users can link the state of data quality directly to the Alation catalog, providing greater visibility and reporting capabilities. This enables organizations to incorporate data quality metrics into their governance workflows, ensuring compliance with mandatory reporting requirements.

Refer to the following sample queries for retrieving heath data:

Select by Quality and Value

Replace the value of <integer_value> with the actual value.

SELECT *
FROM public.data_quality
WHERE quality = 'GOOD'
 AND value::int > '<integer_value>';

Select by object_id

Replace the value of object_id with the actual value.

SELECT *
FROM public.data_quality
WHERE object_id = '<object_id>';

Select by object_type

Replace the value of object_type with the actual value.

SELECT *
FROM public.data_quality
WHERE object_type = '<object_type>';

Select by last_updated

This could be records updated after a certain date. Replace the value of last_updated with the actual value.

SELECT *
FROM public.data_quality
WHERE last_updated > '<YYYY-MM-DD HH:MM:SS.SSS>';

Combined Query (Filter by object_type and last_updated)

Replace the values of last_updated and object_type with the actual values.

SELECT *
FROM public.data_quality
WHERE object_type = '<object_type>'
AND last_updated > '<YYYY-MM-DD HH:MM:SS.SSS>';

Select Records Updated Within a Specific Range

Replace the value of last_updated timestamp with the actual value.

SELECT *
FROM public.data_quality
WHERE last_updated BETWEEN '<YYYY-MM-DD HH:MM:SS.SSS>' AND '<YYYY-MM-DD HH:MM:SS.SSS>';