Data Governance in Live Query
Live Query enables you to work directly with data in supported cloud data platforms (CDPs) without moving or replicating the full dataset into the Alteryx One environment.
For CDP-native processing, Live Query processes the full dataset in your CDP using the platform's compute resources. Alteryx generates the SQL required for supported workflow operations, and your CDP executes the SQL.
How Live Query Processes Data
When your source table is already in the CDP and your workflow uses a single CDP, the full dataset remains in the CDP for processing.
Some Live Query operations require data movement:
Some operations can move data outside its original location. For cross-platform and non-CDP input behavior, go to Use Multiple CDPs in Live Query. For design-time preview behavior, go to Interactive Results Grid.
CDP Datasets
When you register a CDP table as a dataset, Alteryx stores a pointer to the table and its resolved schema information.
This information includes:
Connection information.
Database schema and table information.
Columnn Names
Datatypes
The underlying CDP table isn't copied into Alteryx storage as part of dataset registration. For CDP tables, the registered dataset consists of metadata and a pointer to the source data.
File-Based Datasets
File-based imported datasets behave differently from CDP tables.
For an imported file, the dataset consists of metadata, a pointer, and the file itself. The file persists in configured base storage. The location of the base storage depends on the workspace configuration and deployment.
Information Stored by Alteryx
Alteryx stores information required to define and manage Live Query datasets, workflows, and jobs, including:
Connection metadata
Dataset metadata, including column names and data types.
Workflow definitions.
Job metadata and status history.
Generated SQL.
Query tags.
User and workspace attribution.
A workflow definition contains information such as tool configurations, expressions, column references, and references to datasets and connections.
Workflow definitions don't normally contain dataset row data. However, values entered directly into the workflow, such as values in a Text Input tool or hardcoded filter literals, can become part of the workflow definition.
Live Query Across Deployment Models
The core Live Query pushdown execution model is consistent across supported deployment models. The customer's CDP executes the SQL generated for supported Live Query operations.
The customer's CDP and its region determine where CDP-side data and processing reside.
The deployment configuration determines where Alteryx-side services and configured base storage reside.
Information That Persists After Workflow Execution
Depending on the workflow, the following information can remain after execution:
Information | What its remain |
|---|---|
Output Tables | Customer's CDP |
Output Files | Configured base storage |
Workflow Definitions | Alteryx |
Dataset metadata, including column names and data types | Alteryx |
Job history and metadata | Alteryx |
Query Tags | Alteryx |
SQL Query History | Customer's CDP, according to the CDP's query-history policies |