Querying and query builders
Select SQL Database And Schema Scope
Keep database and schema context on the query tab instead of repeating session-selection statements.
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
Open a SQL tab from the target
Explorer actions initialize the connection, environment, and available database/schema context on the tab.
SQL query results. Editor, result grid, messages, and row selection in one workspace. Open full size - 2
Choose database or catalog
Use the database selector only for engines with a safe supported routing/session mechanism. Other engines keep connection-level or qualified-name behavior.
Object explorer. Datastore-owned tree with native objects and context actions. Open full size - 3
Choose the schema
The selected schema drives object completion and generated qualification. Oracle uses it as the authoritative completion owner.
- 4
Write only the query
The tab applies supported session scope automatically, so generated builder SQL does not prepend a user-authored USE statement.
- 5
Verify the visible context
Connection, environment, database/schema, and environment color remain attached to the tab, including while inactive or moved between windows.
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. |