Guardrails for Query Service
Guardrails are thresholds that guide data and system usage, performance optimization, and avoidance of errors or unexpected results in Adobe Experience Platform.
This document provides default usage limits for Query Service data to help you optimize system performance when querying data in relation to your licensing entitlements.
Prerequisites
Before continuing with this document, you should have a good understanding of the key Query Service definitions and capabilities. They are described below:
-
Ad hoc queries: For executing
SELECT
queries to explore, experiment, and validate data where the results of the queries are not stored on the data lake. -
Batch queries: For executing
INSERT TABLE AS SELECT
andCREATE TABLE AS SELECT
queries to clean, shape, manipulate, and enrich data. The results of these queries are stored on the data lake. The metric for measuring the consumption of this functionality is computational hours. -
Query Service users: Query Service users provided within your current license for Customer Journey Analytics, Adobe Real-Time Customer Data Platform, and/or Adobe Journey Optimizer may also be used with Data Distiller. Query Service users are shared between features.
-
Ad hoc users: Ad hoc users are the ones executing ad hoc queries.
-
Batch users: Batch users are the ones executing batch Queries.
-
Reporting API: An API for making data fetch calls (internally or externally). Extended reporting data models are derived from the native reporting data models in Adobe Experience Platform such as the Real-Time CDP dashboards data model.
The illustration below summarizes how Query Service capabilities are currently packaged and licensed:
Guardrail types
There are two types of default limits within this document:
Primary entity performance guardrails
The tables below provide the recommended guardrail limits and descriptions for query execution when using a particular query pattern.
Ad hoc queries
- As specified in the application product description.
- +5 (with every additional Ad hoc query users add-on pack purchased)
Session Limit Reached
error.- As specified in the application product description.
- +1 (with every additional Ad hoc query user add-on SKU pack purchased)
Client Connector
- Query UI (100 rows)
- Third-party client (50,000)
- PostgresSQL client (50,000)
The result of a query can be received through the following means:
- Query Service UI
- Third-party client
- PostgresSQL client
Note: Adding a limitation to the output count may return results faster. For example, LIMIT 5
, LIMIT 10
, and so on.
Batch queries
The processing time of a query is dependent on the volume of data to be processed and query complexity.
- As specified in the application product description.
- +5 (with every additional Ad hoc query users add-on pack purchased)
Session Limit Reached
error.Client Connector
- Query UI (no upper limit to rows)
- Third-party client (no upper limit to rows)
- PostgresSQL client (no upper limit to rows)
- REST APIs (no upper limit to rows)
The result of a query can be made available using the following methods:
- Can be stored as derived datasets
- Can be inserted into the existing derived datasets
Note: There is no upper limit to the record count number from the query result.
Query accelerated store query-accelerated-store
The table below provides the recommended guardrail limits and description for the query accelerated store.
If you access the reporting API through a BI tool and need more concurrency, a BI server is required.
Next steps
After reading this document you should have a better understanding of the default limits for query execution with the available query patterns.
See the following documentation for more information on Query Service:
See the following documentation for more information on other Experience Platform services guardrails, on end-to-end latency information, and licensing information from Real-Time CDP Product Description documents:
- Real-Time CDP guardrails
- End-to-end latency diagrams for various Experience Platform services.
- Real-Time Customer Data Platform (B2C Edition - Prime and Ultimate Packages)
- Real-Time Customer Data Platform (B2P - Prime and Ultimate Packages)
- Real-Time Customer Data Platform (B2B - Prime and Ultimate Packages)