Guardrail types

There are two types of default limits within this document:

Guardrail typeDescription
Performance guardrail (Soft limit)Performance guardrails are usage limits that relate to the scoping of your use cases. When exceeding performance guardrails, you may experience performance degradation and latency. Adobe is not responsible for such performance degradation. Customers who consistently exceed a performance guardrail may elect to license additional capacity to avoid performance degradation.
System-enforced guardrails (Hard limit)System-enforced guardrails are enforced by the Real-Time CDP UI or API. These are limits that you cannot exceed as the UI and API will block you from doing so or will return an error.
NOTE
The default limits outlined in this document are constantly being improved. Please check back regularly for updates.

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

GuardrailLimitLimit typeDescription
Maximum execution time10 minutesSystem-enforced guardrailThis defines the maximum output time for an ad-hoc SQL query. Exceeding the time limit to return a result throws the error code 53400.
Concurrent Query Service users
  • As specified in the application product description.
  • +5 (with every additional Ad hoc query users add-on pack purchased)
System-enforced guardrailThis defines how many users can create sessions concurrently for a particular organization. If the concurrency limit is exceeded, the user receives a Session Limit Reached error.
Query concurrency
  • As specified in the application product description.
  • +1 (with every additional Ad hoc query user add-on SKU pack purchased)
System-enforced guardrailThis defines how many queries can be executed concurrently for a particular organization. If the concurrency limit is exceeded, the queries are queued.
Client connector and result output Limit

Client Connector

  • Query UI (100 rows)
  • Third-party client (50,000)
  • PostgresSQL client (50,000)
System-enforced guardrail

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.

Results returned viaClient UIN/AThis defines how the results are made available to the users.

Batch queries

GuardrailLimitLimit typeDescription
Maximum execution time24 hoursSystem-enforced guardrailThis defines the maximum execution time for a batch SQL query.
The processing time of a query is dependent on the volume of data to be processed and query complexity.
Concurrent Query Service Users for Unscheduled Batch
  • As specified in the application product description.
  • +5 (with every additional Ad hoc query users add-on pack purchased)
System-enforced guardrailFor unscheduled batch queries (for example CTAS/ITAS queries in interactive mode), this defines how many users can create sessions concurrently for a particular organization. If the concurrency limit is exceeded, the user receives a Session Limit Reached error.
Concurrent Query Service Users for scheduled BatchNo user limitationN/AScheduled batch queries are asynchronous jobs so there is no user limitation.
Computational hours for batch data processingAs specified in the Customer’s Adobe Experience Platform Intelligence Query Custom SKU Sales orderPerformance guardrailThis defines the scoped amount of computational time per year a customer is allowed for executing batch queries to scan, process, and write data back into the data lake.
Query concurrencySupportedN/AScheduled batch queries are asynchronous jobs, therefore concurrent queries are supported.
Client connector and result output limit

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)
System-enforced guardrail

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.

Results returned viaDatasetN/AThis defines how the results are made available to the users.