Query Service packages

This document outlines the different types of packaging and query execution capabilities available in Query Service.

Adobe Experience Platform Query Service can be divided into two capabilities based on the query patterns that can be executed:

  • Ad hoc queries are SQL queries used to explore ingested datasets for verification, validation, experimentation, and so on. These queries do not write data back into the Platform data lake.
  • Batch queries are SQL queries used to perform the post-ingestion processing of ingested datasets. These queries clean, shape, manipulate, and enrich data, the results of which are written back to the Platform data lake. These queries can be scheduled, managed, and monitored as batch jobs.

Query Service capabilities are packaged with the following products and add-ons:

  • Platform-based applications (Adobe Real-Time Customer Data Platform, Adobe Customer Journey Analytics, and Adobe Journey Optimizer): Query Service access to execute ad hoc queries is provided from the outset with every variation and tier of Platform-based applications.
  • Data Distiller (add-on package that can be purchased with Adobe Real-Time CDP, Customer Journey Analytics and Adobe Journey Optimizer): Query Service access to execute batch queries is provided with Data Distiller.

The following table outlines the key Query Service entitlements based on how they are packaged:

Query Service Entitlement Packaged with Platform-based applications Packaged with Data Distiller
Query Pattern Supported Ad hoc query only Batch query
Use Case Supported
  • Exploration​
  • Data Discovery​
  • Data Validation
  • Experimentation
  • Cleaning
  • Shaping
  • Manipulating
  • Enriching
Semantics Supported
  • SELECT queries
  • CTAS and ITAS queries
Maximum Execution Time 10 minutes 24 hours
License Metric Query User Concurrency:
  • 1 concurrent user (Real-Time CDP, Adobe Journey Optimizer)​
  • 5 concurrent user (Customer Journey Analytics)​
Query Concurrency:
  • 1 concurrent running query (all applications)​
Additional ad hoc query users pack add-on can be purchased to increase customers’ authorized ad hoc query entitlements.
  • +5 additional concurrent users per pack
  • +1 additional concurrent running query per pack
Compute Hours:
  • Variable (scoped based on customer’s application entitlements)
Compute Hours is a measure of the amount of time taken by the Query Service engine to read, process, and write data back into the data lake when a batch query is executed.
Query Execution Interface
  • Query Service UI
  • Third-party client UI
  • PostgresSQL client UI
  • Query UI
  • Third-party client UI
  • PostgresSQL client UI
Query Results Returned Via Client UI Derived dataset stored in data lake
Result Limit
  • Query UI - 100 rows
  • Third-party client - 50,000
  • PostgresSQL client - 50,000
  • Query UI (no upper limit to rows)
  • Third-party clients (no upper limit to rows)
  • PostgresSQL client (no upper limit to rows)
  • REST APIs (no upper limit to rows)
Read Dataset Capacity Yes Yes
Write Dataset Capacity No Yes
Scheduling Capacity No Yes
Monitoring Capacity Yes Yes
Query Alert Setup Capacity No Yes

Access control

Access control for Experience Platform is administered through the Adobe Admin Console where product profiles link users with permissions and sandboxes. See the access control overview for more information.

In order to use Query Service, the Manage Queries permission must be enabled within admin console. This permission allows users to execute ad hoc and batch queries. Detailed instructions for requesting access to the product profile Manage Queries permission have been outlined in the manage permissions for a product profile and manage users for a product profile documents.

After purchasing the Data Distiller add-on, the Write Dataset permission must be granted. This permission allows Data Distiller users to execute batch queries.

The following table outlines the effects of the Manage Queries permission:

Permission Function
Manage Queries (without write data permission) Provides access to execute ad hoc queries
Manage Queries (with write data permission) Provides access to execute batch queries

Sandbox support

Sandboxes are virtual partitions within a single instance of Experience Platform. Each Platform instance supports multiple productions and non-production sandboxes, each maintaining its own library of Platform resources. Non-production sandboxes allow you to test features, run experiments, and make custom configurations without impacting your production sandboxes. For more information on sandboxes, see the sandboxes overview. All Query Service entitlements are shared across all sandboxes

Next steps

By reading this document, you should have a better understanding of the different packaging types and query execution capabilities available in Query Service. To learn more about Query Service, such as well-known industry use cases, please read the use case documentation. For more general information, visit the Query Service overview.

On this page