Add a Computed Table
Add a Computed Table to a JDBC source datastore. The Computed Table becomes a container inside that datastore, alongside the base tables and views, and can be profiled and monitored like any other container.
Related
- Concept: Introduction for what a Computed Table is.
- Mechanics: How It Works for validation, referencing rules, and execution.
- Comparison: Computed Table vs Computed File if you are not sure which one you need.
Field Reference
Every field on the Add Computed Table modal, in three sections that mirror the layout of the form.
| REF. | Field | Description |
|---|---|---|
| 1 | Name (Required) | A descriptive, meaningful name for the Computed Table (for example, patient_lifetime_value). Spaces are replaced with underscores automatically. Must be unique inside the datastore. |
| 2 | Query (Required) | A valid SQL statement in the parent datastore's dialect. The query can reference any physical table or view in this datastore. Fully-qualified names (SCHEMA.TABLE) are required for SQL Server, Oracle, and Redshift. Press Ctrl+Space inside the editor for hints. See How It Works for the full referencing rules. |
| REF. | Field | Description |
|---|---|---|
| 3 | Suggest | Generates an AI description for the Computed Table based on the current form values. Only visible when an LLM provider is configured under AgentQ. See Description Suggestions for the full workflow. |
| 4 | Description (Optional) | A short business summary of what the Computed Table represents. |
| REF. | Field | Description |
|---|---|---|
| 5 | Owner (Required) | The Qualytics user who owns this Computed Table. Defaults to you. Only users with the Editor team permission can assign a different owner; users with the Author team permission can create Computed Tables they own but cannot reassign later. |
| 6 | Additional Metadata (Optional) | Custom key-value pairs. Click the plus icon to open the editor and add rows. |
Fully-qualified names
On SQL Server, Oracle, or Redshift datastores, the query must reference every table with its fully-qualified name (SCHEMA.TABLE). Unqualified names on these connectors will fail at Validate or Save.
Steps
Step 1: Click the Add button in the top-right of the datastore overview.
Step 2: A dropdown appears with the containers you can add to a JDBC datastore.
Step 3: Select Computed Table.
Step 4: The Add Computed Table modal opens. See the Field Reference above for what each input controls.
Step 5: Fill in the fields. Name and Query are required; Description, Owner, and Additional Metadata are set as needed.
Step 6: Click Validate. Qualytics sends the SQL to the warehouse for a parse and semantic check: the syntax must be valid in the connector's dialect, and every referenced table, view, and column must exist and be readable with the datastore's connection credentials.
If validation fails, the modal surfaces the warehouse's own error message so you can fix the query in place. Running Validate is optional; if you skip it, Qualytics validates the query as part of the Save request and surfaces any error inline.
Step 7: Once the validation success message appears, click Save.
Step 8: A success message confirms the creation and the new Computed Table appears in the datastore's containers list. Qualytics automatically runs a slim profile of up to 1000 records per partition so you can see field statistics right away, followed by a full profile in the background.
