Use DBeaver as an ad-hoc SQL client against Delta Forge through the ODBC driver.
Database > New Database Connection > ODBC## Setup 1. Install the Delta Forge ODBC Driver. DBeaver does not ship its own driver manager; on Linux it uses unixODBC, on macOS it uses iODBC, on Windows it uses the OS driver manager. 2. **Database** -> **New Database Connection** -> **ODBC** -> **Next**. 3. Choose **DeltaForge ODBC Driver** from the **Driver** dropdown. DBeaver enumerates the OS-registered ODBC drivers automatically. 4. Either pick an existing DSN or fill in the connection string. The **Connection settings** dialog has tabs for **Main**, **SSH**, and **Initialization**; the **Main** tab's **JDBC URL** field doubles as a connection-string box for the ODBC bridge. 5. **Test Connection**. ## Catalog navigation The Database Navigator on the left shows the zones / schemas / tables tree. Drilling expands one level at a time; DBeaver issues `SQLTables` and `SQLColumns` lazily so opening a deeply nested tree is fast. ## Running SQL - **F5** or the **Execute SQL Query** button runs the statement under the cursor. - **Alt+X** runs the entire script. - Results land in the bottom pane; the **Save / Filter / Group** controls work locally on the result set without round-tripping to the engine. ## ODBC support across DBeaver editions ODBC connection support varies by DBeaver edition and release; if the **ODBC** option is missing from your **New Database Connection** dialog, consult the DBeaver release notes for that version. Delta Forge does not ship a JDBC driver in the current version. ## Saving credentials DBeaver caches connection credentials in its own encrypted store. The **Save password locally** toggle is per-connection. If you also store the password in the OS keychain through the Delta Forge DSN setup GUI, omit `Pwd=` from the DBeaver connection so the driver-side keychain lookup wins; this lets credential rotation happen in one place.
# Standard ODBC route
DSN=DeltaForge;Uid=alice@example.com;Pwd=hunter2