Query Service packaging
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.
Entitlements entitlements
The following table outlines the key Query Service entitlements based on how they are packaged:
- Exploration
- Data Discovery
- Data Validation
- Experimentation
- Cleaning
- Shaping
- Manipulating
- Enriching
- SELECT queries
- CTAS and ITAS queries
Query User Concurrency:
- 1 concurrent user (Real-Time CDP, Adobe Journey Optimizer)
- 5 concurrent users (Customer Journey Analytics)
Query Concurrency:
- 1 concurrent running query (all applications)
An additional ad hoc query users pack add-on can be purchased to increase your authorized ad hoc query entitlement.
- +5 additional concurrent users per pack
- +1 additional concurrent running query per pack
Compute Hours:
- Variable (scoped based on your application entitlement)
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.
With the Data Distiller SKU, you also get an additional user and query concurrency, which can be used towards the execution of ad hoc queries. The Data Distiller SKU includes:
- +5 additional concurrent users
- +1 additional concurrent running query
Your data lake storage capacity is measured in terabytes (TB) and depends on the quantity of Compute hours that you have bought. Check the product description for more details.
Your annual data export allowance is measured in terabytes (TB) and depends on the quantity of Compute hours that you have bought. Please check product description for more details.
- Query Service UI
- Third-party client UI
- PostgresSQL client UI
- Query Service UI
- Third-party client UI
- PostgresSQL client UI
- REST APIs
- Query Service UI - The number of output rows can be configured with a UI setting to between 50-500 rows.
- Third-party clients - 50,000
- PostgresSQL client - 50,000
Access control 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.
See the Manage permissions for a product profile and Manage users for a product profile documents for detailed instructions on requesting access to the product profile permissions
Relevant Query Service permissions query-service-permissions
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.
The following table outlines the effects of the Manage Queries permission:
Relevant Customizable Insights permissions customizable-insights-permissions
To create Data Distiller Customizable Insights within dashboards, the following permissions must be enabled within Admin Console.
Sandbox support sandbox-support
Sandboxes are virtual partitions within a single instance of Experience Platform. Each Platform instance supports multiple production 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, read the use case documentation. For more general information, visit the Query Service overview.