dbDBCraftDocs
Overview
IGetting started
About this guideWhat DBCraft AI Studio isInstallationActivating your licenceConnecting to a databaseA tour of the workspace
IIThe workspace
The menu barThe icon toolbarThe connection chip and container switcherThe docking railThe left panel (cluster drawer)The bottom dockThe status barThe command paletteExtra windows
IIIDevelopment modules
SQL EditorResults grid and data editingGraphsObject Browser and Object ViewerPL/SQL DebuggerUnit Test ManagerReports
IVDBA modules
Schema ToolsVersion HistorySession BrowserDBA Dashboards (Health)Storage BrowserPerformance Profiler and SQL OptimizerIndex AdvisorER Diagram ModelerAutomation and JobsLoad Tester
VTools and utilities
SQL TerminalAI AssistantExport Tables and Import Tables
VIConfiguration and reference
Settings referenceKeyboard shortcutsLicence managementLogging, diagnostics and bug reportsSecurity and data handlingTroubleshootingFile and folder locationsBackend API referenceGlossary
Documentation/Tools and utilities
Chapter 33

SQL Terminal

A SQL*Plus-style console. Open it from the bottom dock (Ctrl+`), the Terminal menu, or as a standalone window.

#33.1The login sequence

The terminal boots exactly like the real thing — a banner, then:

text
Enter user-name:
Enter password:

The password is never echoed. On success it prints Connected to: followed by the database’s own version banner, then the SQL> prompt.

Press Enter at the empty user-name prompt to reuse the active IDE connection’s account. This is the fastest way in.

If the account cannot read V$VERSION, the terminal probes with SELECT user FROM dual before deciding the login failed — a login with limited privileges still works.

#33.2Entering statements

  • A statement ends with ;. Until then, lines keep buffering and the prompt becomes a line number, exactly like SQL*Plus.
  • / on its own line runs the buffered block — use this for PL/SQL, where the semicolons are part of the code.
  • A blank line discards the buffer.
  • Ctrl+C with no selection also clears the buffer.

#33.3Built-in commands

CommandAction
<statement>;Run a SQL statement (multi-line until ;).
/Run the buffered PL/SQL block.
desc <object>Describe a table or view — name, type (with length/precision) and nullability. Accepts SCHEMA.OBJECT.
connect (conn)Log in as a different user.
disconnect (disc)Log out of the current session.
show userPrint the current user.
historyList the statements run in this console.
clear / clsClear the screen.
helpPrint the command list.
exit / quitClose the terminal.

#33.4Output and history

Query results are printed as aligned text tables. Long values are truncated at 40 characters; at most 200 rows are printed, with a note about how many were omitted, followed by the total row count. Every statement reports Elapsed: n.nns.

↑ and ↓ walk the statement history when the buffer is empty.

The header bar shows the connected user and host, a Clear terminal button and a Close panel button. The console keeps its classic dark palette regardless of the application theme.

The terminal uses its own auto-committed connection. It does not see the SQL editor’s uncommitted rows, and statements you run here commit immediately.