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:
Query Service capabilities are packaged with the following products and add-ons:
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||
|Maximum Execution Time||10 minutes||24 hours|
|License Metric||Query User Concurrency:
|Query Execution Interface||
|Query Results Returned Via||Client UI||Derived dataset stored in data lake|
|Read Dataset Capacity||Yes||Yes|
|Write Dataset Capacity||No||Yes|
|Query Alert Setup Capacity||No||Yes|
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:
|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|
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
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.