Datastore-specific guides
SQL Family Workflows
Work with PostgreSQL, SQL Server, MySQL, MariaDB, SQLite, CockroachDB, TimescaleDB, DuckDB, Oracle, and related engines.
Prerequisites
- Install the current DataPad++ desktop pre-release and open the workspace where you want to organize your connections and saved work.
- Have access to a datastore or database file you are authorized to inspect. Start read-only with a least-privileged account.
Quickstart
- 1
Create a typed SQL connection
Choose the specific engine so DataPad++ can apply the right dialect, metadata surfaces, disabled reasons, and guarded operation previews.
Object explorer. Datastore-owned tree with native objects and context actions. Open full size - 2
Explore schemas and tables
Open databases, schemas, tables, views, columns, indexes, routines, roles, diagnostics, or engine-specific tree sections.
SQL query results. Editor, result grid, messages, and row selection in one workspace. Open full size - 3
Open a scoped query
Use table or view actions to start with a SELECT builder or raw SQL editor already aimed at the selected object.
Security settings. Global safe mode explains how risky writes, inline edits, API and MCP requests, and read-only work are guarded. Open full size - 4
Inspect plans and diagnostics
Use EXPLAIN, profile, wait, lock, storage, query-store, performance-schema, or engine-specific panels where available.
- 5
Edit rows with identity proof
Live row edits require primary-key or equivalent identity context plus read-only and environment checks.
- 6
Keep admin work preview-first
Maintenance, role, extension, backup, restore, import, export, and destructive workflows should show guarded plans before execution.
Task and control reference
The workbench keeps the active connection, environment, target scope, query mode, and panel state visible. Review that context before you run, edit, export, or administer anything.
Safety boundaries
Troubleshooting
| Symptom | What to check |
|---|---|
| A control is disabled | Read its disabled reason, then verify target scope, connection health, read-only mode, environment policy, and feature maturity. |
| The screen does not match this guide | Confirm the app version and platform, refresh the active tab, and check whether the feature is marked Experimental, Plan only, or Unavailable. |
| The operation produces no rows | Open Messages and History, verify the selected datastore scope, replace the sample object names with names from your datastore, and retry with a bounded read. |