SQLlightspeed brings the whole Oracle development lifecycle into one application: writing code, compiling, debugging, performance analysis, regression testing, object comparison and database administration. It is a native Windows and macOS application that does not slow down on very large enterprise application databases.
Editor · debugger · profiler · tests · DBA
First index ready in under a second
A native application on both
-- own Oracle session per worksheet select c.order_no, c.customer_no, c.state, c.wanted_delivery_date from erpapp.customer_order_tab c where c.state in ('Released', 'Reserved') and c.wanted_delivery_date < sysdate + 7
| Order no | Customer | State | Wanted delivery | Lines |
|---|---|---|---|---|
| CO-104871 | NORTHLINE | Released | 2026-09-04 | 14 |
| CO-104872 | HARBOUR-LG | Released | 2026-09-04 | 6 |
| CO-104880 | AEGEAN-MT | Reserved | 2026-09-05 | 31 |
Measured in the reference installation.
A package change is written in one tool, compiled in another, debugged in a third and its plan read in a fourth. What the change broke in Test or Production is usually discovered on deployment night.
SQLlightspeed puts that whole loop in one window — write, compile, see the error on its line, step through it, measure its profile, run the regression set and see the Dev–Test–Prod difference before the release, not during it.
Nothing is installed on the server side; no Instant Client, no Java.
On the Mac, no virtual machine and no remote desktop.
Not a single object in your schema changes.
Not a SQL editor, and not a web console. The whole Oracle working day happens in one application: from the object tree to the DBA panels, from the compile loop to the explain plan. Every worksheet runs in its own Oracle session — a long-running query never blocks another tab.
Code Assistant suggests columns, parameters and package elements as you type; code folding, hyperlink navigation and the PL/SQL Beautifier keep large packages readable. ⌘P search across hundreds of thousands of objects answers in under 50 milliseconds per keystroke — the metadata sits in a local index on disk, not in a memory dump.
| PACKAGE BODY | CUSTOMER_ORDER_API | ERPAPP · 18,402 lines |
| TABLE | CUSTOMER_ORDER_TAB | ERPAPP |
| VIEW | CUSTOMER_ORDER_LINE | ERPAPP |
| TRIGGER | CUSTOMER_ORDER_TR | ERPAPP |
| TEXT | … Customer_Order_API.Get_State(order_no_) | 3,118 source matches |
You compile from the editor and the error lands on its exact line. The integrated debugger steps through procedures, functions, packages and triggers; variable values and the call stack are on the same screen. A test block with prefilled parameters is generated for any procedure.
212 if state_ = 'Released' then 213 qty_ := Get_Reserved_Qty___(order_no_); 214 if qty_ < line_qty_ then Error_SYS.Record_General(…);
The PL/SQL Profiler shows how long each line took; SQL statistics and explain-plan cost bars mark the risky step. The reason slow code is slow comes from a measurement, not a hunch.
| Line | Source | Calls | Total |
|---|---|---|---|
| 1,144 | Get_Reserved_Qty___ | 31 | 3.41 s
|
| 1,207 | Check_Credit_Limit___ | 31 | 0.92 s
|
| 1,318 | Log_History___ | 31 | 0.31 s
|
| Operation | Object | Rows |
|---|---|---|
| HASH JOIN | — | 74,070 |
| TABLE ACCESS FULL | CUSTOMER_ORDER_TAB | 22,821 |
Cost does not come from large projects. It comes from small, quiet changes: one extra parameter on a package, an index that exists in Test but not in Prod, a trigger whose firing order moved. SQLlightspeed stops at exactly those three points.
Object compare checks packages, views, triggers, indexes and grants across two environments; the differences appear in one list before the release, together with the DDL needed to align them. The surprise arrives in the morning, not at midnight.
| Type | Object | Difference | Action |
|---|---|---|---|
| PACKAGE | CUSTOMER_ORDER_API | source differs ×3 | deploy |
| INDEX | CUST_ORDER_STATE_IX | missing in target | missing |
| TRIGGER | CUSTOMER_ORDER_TR | fire order moved | deploy |
| GRANT | ORDER_MANAGER | not granted | missing |
Test Manager re-runs saved test sets after a change; every scenario that deviates from its expected output is listed by name and opens straight in the debugger. “What does this change break?” becomes a report instead of a guess.
The DBA panels gather sessions, the blocking-lock tree, tablespace growth, scheduler jobs, invalid objects, AQ queues, parameters and the recycle bin in one tab. Invalid objects are recompiled in bulk in a single action.
| SID | User | Status | Wait event | Sec | Blocker |
|---|---|---|---|---|---|
| 7,045 | APPSYS | active | db file seq read | 3 | — |
| 4,201 | ERPAPP | blocked | enq: TX row lock | 128 | 7,731 |
| 7,731 | RPT_USR | active | SQL*Net from client | 131 | — |
Speed was not added later; it was put in the foundation.
SQLite with full-text search. Hundreds of thousands of objects ≈ 25 MB; queries are measured in milliseconds.
Tauri 2 over the operating system’s own web view. No bundled browser, a small binary.
Oracle Instant Client and Java are not required. The app carries its own runtime.
There is one standard: if a feature stutters, that feature is not done. Performance claims are verified with a stopwatch and an automated suite, and the interface never blocks — not even while indexing runs.
For teams whose day is spent inside Oracle.
Speed is no excuse for carelessness.