Skip to main content
Administrator Guide
Last Updated: 2026-11-13
Get Started with Workday Live Data Query

Get Started with Workday Live Data Query

You might need to take additional steps to enable this feature depending on your organization's subscription service agreement. For more information, see this Community article.

Overview

Workday Live Data Query (LDQ) enables real-time SQL access from external systems to Workday's core business objects without using ETL or data replication. External clients query data within Workday on demand through a JDBC or Python driver.
Follow these steps to get started with LDQ:
  1. Configurate Authentication in Workday
  2. Connect from External Client
  3. Review the Data Cloud Catalog
  4. Query Workday Data

Step 1: Configure Authentication in Workday

Familiarize yourself with LDQ authentication below and configure the authentication method that suits your needs.
Image comparing the 2 Live Data Query authentication methods: Integration System User and User As Self.
You can set up your LDQ connection with either of these authentication methods:
Integration System User (ISU)
User As Self (UAS)
Description
Allows the external system to authenticate as a dedicated, non-person system account. Access to data is limited to the tables and columns authorized for the ISU through domain permissions.
User logs in through a browser session to authenticate the connection. Data access is determined by user’s permissions according to Workday's full security model.
Security Scope
Tables, Columns
Tables, Columns, Rows, Cells, Contextual Security
Security Controls
Unconstrained security groups > Domain permissions
  • Full Workday security model enforced externally.
  • Functional area scope configured on API client.
OAuth Mechanism
Public/private key pair.
Client ID, client secret, and browser-based login.
Suggested Usage
Data platforms (Example: Snowflake)
  • Analytics tools (Example: Tableau)
  • AI/LLMs/Agents (Example: Gemini)
Setup Instructions

Step 2: Connect from External Client

After you set up LDQ authentication, you can connect to LDQ from your external system. As a starting point, we recommend attempting a connection from DBeaver first.
Live Data Query offers these combinations of external clients and drivers:
External Client
Driver Download
Setup Instructions
DBeaver
AWS (Glue, Athena)
Custom connector
Tableau
Python
Snowflake
Power BI
Contact Workday Support
Databricks
GCP Spark
It’s possible to use LDQ drivers in clients other than those documented here.

Step 3: Review the Data Cloud Catalog

Assess what objects are available to query and the security domains that govern access to them. See Data Cloud Catalog for information how to read the catalog.

Step 4: Query Workday Data

After you’ve established a data connection from the external client with the driver, you can run SQL statements to query Workday data. See Query Workday Data Using Live Data Query.

Guardrails and Limitations

  • These guardrails and limitations are subject to change:
    Maximum Value
    Query Runtime (Execution)
    30 minutes
    Query Runtime (Queueing, Execution, Data Out)
    60 minutes
    Query Concurrency (Per Tenant)
    90 queries
    Query Concurrency (Per Environment)
    100 queries
    Query Queue Length (Per Tenant)
    800 queries
    Query Queue Length (Per Environment)
    1000 queries
    Memory per Query
    20 GB
    Query Request Size (SQL Length)
    1,000,000 characters
    Query Response Size (Per Chunk)
    16 MB
    Query Response Size (Total)
    No limit
    Query Response Cells (Rows, Columns)
    No limit