Nexo SQL Studio
Nexo SQL Studio is a Visual Studio Code extension for Oracle SQL and PL/SQL development. It brings Oracle-aware editing, navigation, execution, testing, and database tooling into one VS Code workflow.
The current release is in public beta.
Watch Nexo SQL Studio Showcase on Youtube
What Nexo SQL Studio includes
- AI-assisted SQL and PL/SQL development with MCP support
- Oracle Apex 26.1+ AI app development, ApexLang problems validation, auto upload modifications.
- Smart PL/SQL autocompletion and IntelliSense for package members, procedures, functions, types, columns, and contextual PL/SQL symbols
- Go to Definition and symbol navigation across package specs, bodies, files, and configured search paths
- Inline SQL and PL/SQL execution with rich results, filtering, sorting, pagination, export, gallery-style previews, and detailed cell inspection
- Connection Explorer and object tree browsing for schemas, tables, views, packages, procedures, functions, sequences, and synonyms
- Object editing and compile workflows directly inside VS Code
- Offline DDL export for file-based workflows, version control, and pull requests
- utPLSQL discovery and execution in the VS Code Test Explorer with inline pass/fail feedback
- SQL and PL/SQL formatting, syntax highlighting, snippets, generated documentation headers, signature help, and hover help
- Multi-connection support, connection groups, schema switching, and SQL Developer connection import
- Managed deployments, automated data migrations, live code validation, and database management workflows
- Integrated step debugger support
- Oracle APEX and ORDS support
- Cross-platform distribution through the VS Code Marketplace on macOS, Windows, and Linux
PL/SQL step debugger
Open a procedure, function, or package body and click the editor gutter beside an executable line to add a normal VS Code breakpoint. For packages, keep breakpoints in the package body. Continue, Step Into, Step Over, Step Out, and Stop are supported and reported in the Debug Console together with session start, readiness, and finish. Pause is rejected explicitly because Oracle DBMS_DEBUG cannot asynchronously interrupt a running call.
Watch entries are case-insensitive local-variable or parameter names from the selected stack frame. For PK_DEBUG.RUN_WORKFLOW, useful entries include p_customer_code, p_amount, p_status, p_priority, l_step, l_discount, and l_net_amount. Enter each name separately; arbitrary PL/SQL expressions and function calls are not evaluated, and nested-block locals appear only while their scope is active.
The Nexo SQL Studio: PL/SQL Debugger settings section contains Stop On Exception, also overridable as stopOnException in a launch configuration. No debugger host, listener port, firewall rule, or JDWP ACL is required. A DBA must grant:
grant execute on sys.dbms_debug to YOUR_SCHEMA;
grant debug connect session to YOUR_SCHEMA;
Cross-schema debugging additionally requires EXECUTE and DEBUG on the target object.
Public Beta
This beta is intentionally focused. The core workflow is already available, but some areas are still evolving and additional capabilities are planned. Install the beta directly from the download page and sign in with Google, Microsoft, or email to start using it for free.
Why teams use it
- Stay in VS Code from discovery to editing, execution, validation, and export
- Work against live Oracle databases or generate local files for offline review and Git-based delivery
- Reduce context switching across object browsing, query execution, test runs, formatting, and navigation
Learn More
| |
