Skip to content

Getting Started with Computed Tables

Computed Tables are SQL-defined virtual containers built on top of the base tables and views of a JDBC source datastore. You write a single SQL query; Qualytics stores the definition and runs it whenever the container is scanned or profiled. The result behaves like any other container: you can profile it, add quality checks, and detect anomalies.

Use Computed Tables to prepare data (clean, shape, restructure), run complex calculations, subset data with a WHERE clause, or join tables inside the same JDBC datastore.

Add Computed Table modal with fields for Name, SQL Query, Description, and Additional Metadata

Permissions

You need the Member user role and one of the following on the parent datastore to add, edit, or delete a Computed Table: the Editor team permission, or the Author team permission when you are (or will be) the owner of the Computed Table. Viewing one requires the Reporter team permission (or above) on the datastore. See the Permissions page for the full matrix.

Deep Dive

  • Introduction

    What a Computed Table is, when to reach for one, and how it differs from a Computed File.

    Introduction

  • How It Works

    Execution model, validation semantics, referencing rules, and the fully-qualified-name requirement for certain connectors.

    How It Works

  • Computed Table vs Computed File

    Side-by-side comparison: when to reach for a Computed Table over a Computed File, and where each one shines.

    Computed Table vs Computed File

  • Incremental Profiling

    Configure Qualytics to scan only rows that changed since the last profile using a timestamp or batch-value field.

    Incremental Profiling

  • Cost and Performance

    Where the cost of a Computed Table lives and how to keep scans and profiles fast on large data.

    Cost and Performance

  • SQL Dialects per Connector

    Connector-specific quirks and the fully-qualified-name list.

    SQL Dialects

  • Permissions

    Who can view, create, edit, delete, reassign, and run operations on a Computed Table. Includes the Author-and-owner hybrid gate.

    Permissions

  • Best Practices

    A checklist for naming, query style, metadata, profiling, ownership, and sunsetting Computed Tables.

    Best Practices

  • Examples

    Real-world Computed Tables across e-commerce, finance, SaaS, and data engineering, with the SQL patterns that fit each scenario.

    Examples

How-tos

  • Add a Computed Table

    Step-by-step walkthrough of the Add Computed Table modal, from datastore selection to Save.

    Add

  • Edit a Computed Table

    Change the SQL query, description, owner, or metadata of an existing Computed Table.

    Edit

  • Delete a Computed Table

    Remove a Computed Table and understand its impact on quality checks, anomalies, and downstream operations.

    Delete

Reference

  • API

    REST endpoints to add, edit, delete, and read Computed Tables programmatically.

    API

  • FAQ

    Answers to common questions about Computed Tables: references, joins, materialization, and connector quirks.

    FAQ