Zero Data Query Results

Alation Cloud Service Applies to Alation Cloud Service instances of Alation

Applies from version 2026.4

This topic applies only to data sources that are configured to use the Query Service Add-on (Zero Data mode). If your organization has not installed the Query Service Add-on, query results continue to work as described in the other topics in this section, and this page does not apply to you.

When the Query Service Add-on is installed on an Alation Agent and a data source is configured to use it, query results work differently from the standard Compose behavior. This topic describes those differences.

How Zero Data Query Results Work

The Zero Data feature lets you execute queries, sampling, and profiling through an on-premises Alation Agent. No query result data traverses or gets stored in Alation Cloud Service. Instead, the Agent writes query results to your own object store (AWS S3 or Azure Blob Storage). Your browser retrieves results directly through a secure gateway running on the Agent.

When you execute a query in Compose against a data source using the Query Service Add-on:

  1. The Agent receives the query and executes it against the data source.

  2. The Agent writes the query results to your object store (AWS S3 or Azure Blob Storage).

  3. Your browser retrieves the results directly from the object store through a secure connection to the Agent.

The actual query result data never passes through or gets stored in Alation Cloud Service.

Zero Data Banner

When you open Compose for a data source configured to use the Query Service Add-on, a banner indicates that the data source is in Zero Data mode. This banner confirms that the Agent stores query results in your object store rather than in Alation.

Features That Behave Differently

The following Compose and query result features behave differently when a data source uses the Query Service Add-on:

Notification Emails

When a scheduled query or long-running query completes, notification emails don’t include download links for the query results. The results reside in your object store and can only be accessed through Alation from your browser.

To view the results, click the link in the email to open the results page in Alation.

Query Result Preservation

In Zero Data mode, the bucket lifecycle policy on your object store replaces the standard Preserve Data behavior:

  • Compose results – Available for the duration specified in the bucket lifecycle policy (recommended: 7 days)

  • Sampling and profiling results – Available for a longer configurable period based on the bucket lifecycle policy

After results expire based on the bucket lifecycle policy, you must re-execute the query to regenerate them. The Preserve Data button doesn’t appear for data sources using the Query Service Add-on.

For help configuring the bucket lifecycle policy, see Configure Bucket Lifecycle Policy.

Result Expiration

Query results expire based on the bucket lifecycle policy rather than Alation’s internal retention settings. After a result expires:

  • The result entry still appears in the query execution history

  • Viewing an expired result displays a message indicating that the result has expired and needs re-execution

Exporting and Downloading Results

Export and download of query results is not supported in Zero Data mode. Query results are stored in your object store and can only be viewed through Alation in your browser.

Data Retention

Note

Zero Data only. If your organization has installed the Query Service Add-on and configured a data source to use it, the bucket lifecycle policy on your object store manages query result retention for that data source, not Alation’s internal retention settings. If you don’t use the Query Service Add-on, the standard retention settings described on this page apply. See Manage the Query Service Add-on for help configuring bucket lifecycle policies.