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/Getting started
Chapter 2

What DBCraft AI Studio is

DBCraft AI Studio is a desktop IDE and DBA toolkit for Oracle Database. It combines, in one window, the tools that a typical Oracle team otherwise spreads across half a dozen applications:

  • a multi-tab SQL and PL/SQL editor with a persistent transaction, autocomplete, formatting and explain plans;
  • a schema browser with DDL generation, script generation, object comparison and data import;
  • a real PL/SQL debugger driven by Oracle’s DBMS_DEBUG — breakpoints, stepping, variables, watches, call stack;
  • a unit test manager for PL/SQL, with suites, expected outputs and performance thresholds;
  • DBA dashboards — live metrics, health scanning, tablespace and datafile browsing, ASM and RAC overviews;
  • session monitoring with a blocking-lock tree and session termination;
  • schema compare and synchronise, DDL export, data import/export;
  • object version history with diffs and one-click restore;
  • an ER diagram modeler that reverse-engineers a schema and can forward-engineer DDL;
  • an index advisor, a SQL profiler/optimizer and a concurrent-session load tester;
  • a workflow automation designer with cron scheduling;
  • a report catalogue with parameters, HTML templates and branding;
  • a SQL*Plus-style terminal;
  • an AI assistant you point at your own AI endpoint.

#2.1How it is built (and why that matters to you)

The application ships as a single Windows program, but internally it has two parts:

  • The user interface — the Electron desktop window you interact with.
  • A local service — a small background process that runs on your own machine, started and supervised by the Electron application. Every database operation goes through it.

Two consequences are worth understanding, because they explain behaviour you will notice:

  1. Nothing leaves your machine. The local service connects directly to your Oracle database. There is no cloud component, no telemetry, no account server. The only outbound connection the product ever makes is the one-off licence activation call (chapter 4), and any calls the AI assistant makes to the AI endpoint you configure (chapter 34).
  2. Most operations are stateless. Each action opens a fresh database connection, does its work, and closes it. This keeps the tool from holding idle sessions on your server. There are three deliberate exceptions, all documented where they matter: the SQL editor’s transaction (§16.6), the debugger’s session (chapter 20), and a test run’s shared session (chapter 21).

If the local service is not running, every panel reports the same thing: "Cannot reach the backend." See chapter 41.

#2.2Where the product stores its own data

DBCraft keeps its own feature data — saved reports, test suites, load tests, object version history — in local database files, entirely separate from the Oracle database you connect to. Your Oracle database is never modified to make DBCraft work; there are no repository tables to install. See Appendix A for exact locations.