SQL client tutorials for six database engines

Choose structured fields or a raw connect string. Use the supplied service name or SID. Oracle Thin mode is the default: Oracle Instant Client is not required for ordinary connections. TNS, TCPS, wallets and external authentication have additional requirements.

Enter the PostgreSQL database name and role. Check schema permissions and TLS requirements. For Supabase, use the direct or pooler details provided by the project; IPv4/IPv6 reachability and pooler behavior can affect your workflow.

Choose the actual engine: MySQL and MariaDB have separate adapters. Enter the database name, user and TLS settings; SQL syntax, server versions and authentication plugins can differ.

Choose the actual engine: MySQL and MariaDB have separate adapters. Enter the database name, user and TLS settings; SQL syntax, server versions and authentication plugins can differ.

Choose a local SQLite database file that you are authorized to access. SQLite does not need a server, port or database-user password. Confirm file access when prompted and check read-only mode before making changes.

Use the SQL Server host, port, database and supported SQL-login credentials. Check encryption and certificate settings. Do not assume Windows integrated authentication, Microsoft Entra authentication or Azure SQL compatibility from SQL-login support alone.

Follow the complete first-run workflow: install Nexo SQL Studio, create a connection, execute SQL, and filter the results.

Create a connection profile, test credentials, and open your first SQL worksheet from VS Code.

Navigate tables, views, packages, procedures, and generated DDL from the Connections Explorer.

Save Oracle object definitions into a project folder so changes can be reviewed and versioned.

Prepare a deployment, review selected objects, and run the deploy flow against a target connection.