Last updated: 2026-02-12

Connections

Connect to SQL Server, Azure SQL, PostgreSQL, MySQL, MariaDB, Oracle, and SQLite databases with Jam SQL Studio. This guide covers supported databases, authentication methods, connection options, and managing your saved connections.

Supported Databases

Jam SQL Studio supports five major database platforms:

Creating a Connection

To create a new database connection:

1. Click the + button in the sidebar, or
2. Go to File > New Connection, or
3. Press Cmd+Shift+N (macOS) / Ctrl+Shift+N (Windows/Linux)

After you save a new connection, it appears at the top of the Recent list in the Saved Connections dialog and at the top of the connections list on the Start Page.

Connection Settings

Fill in the following fields to configure your connection:

• Connection Name - A friendly name for this connection (e.g., "Production DB", "Dev Server")
• Server/Host - The database server address (e.g., localhost, localhost\\SQLEXPRESS, 192.168.1.100, myserver.database.windows.net)
• Port - Server port (defaults: SQL Server 1433, PostgreSQL 5432, MySQL 3306, Oracle 1521). For SQL Server named instances (e.g., localhost\\SQLEXPRESS), leave Port blank to auto-resolve the instance port (requires SQL Browser).
• Database - The default database to connect to (optional)
• Authentication - Choose your authentication method

Authentication Methods

Jam SQL Studio supports multiple authentication methods depending on your database type.

SQL Server Authentication

Use a SQL Server login and password:

1. Select SQL Server Authentication from the dropdown
2. Enter your Username (e.g., sa or your login name)
3. Enter your Password
4. Check Remember Password to save credentials securely

Windows Authentication

Use your Windows credentials (available on Windows only):

1. Select Windows Authentication from the dropdown
2. Your current Windows user will be used automatically
3. No username or password required

Azure Entra ID (Azure Active Directory)

For Azure SQL Database and Azure SQL Managed Instance:

1. Select Azure Entra ID from the dropdown
2. Click Sign In to open the browser authentication flow
3. Complete the Microsoft login in your browser
4. Return to Jam SQL Studio - you'll be connected automatically

PostgreSQL Authentication

For PostgreSQL connections:

• Password - Standard username/password authentication
• SSL/TLS - Encrypted connections with optional client certificates

SSL Connection Options

• SSL Mode - Choose from: disable, require, verify-ca, verify-full
• CA Certificate - Path to the certificate authority file
• Client Certificate - Path to client certificate (for mutual TLS)
• Client Key - Path to client private key

MySQL / MariaDB Authentication

For MySQL and MariaDB connections:

• Password - Standard username/password authentication (default user: root)
• No Password - Connect without a password (for local development servers)

SSL Connection

Enable the SSL checkbox for encrypted connections. This is recommended for remote MySQL servers and required by many cloud-hosted MySQL services.

Oracle Authentication

For Oracle Database connections:

• Password - Standard username/password authentication (default port: 1521)
• SSL/TLS - Encrypted connections via the SSL checkbox
• Wallet (mTLS) - For Oracle Autonomous Database (ADB) cloud connections using a wallet directory

Connection String Types

Oracle supports three connection string formats:

• EZConnect (default) - Simple host:port/service_name format
• TNS Descriptor - Full TNS connection string for advanced configurations
• TNS Alias - Named alias resolved from a tnsnames.ora file

Service Name vs SID

By default, connections use a Service Name. Toggle to SID if your database uses a System Identifier instead. Modern Oracle databases (12c+) prefer service names.

SQLite Connections

SQLite uses file-based storage with no authentication:

1. Select SQLite as the database type
2. Click Browse to select your .sqlite or .db file
3. Click Connect to open the database

Connection Options

Expand the Advanced Options section to configure additional settings:

General Options

• Connection Timeout - Seconds to wait before timing out (default: 15)
• Command Timeout - Seconds to wait for query execution (default: 30)

Security Options (SQL Server)

• Encrypt Connection - Use TLS encryption for data in transit (recommended)
• Trust Server Certificate - Accept self-signed certificates (development only)

Managing Connections

Jam SQL Studio saves your connections for quick access.

Saving Connections

1. Fill in all connection details
2. Enter a meaningful Connection Name
3. Click Test Connection to verify settings
4. Click Save to store the connection

Editing Connections

1. Right-click a saved connection in the sidebar
2. Select Edit Connection
3. Modify settings as needed
4. Click Save to update

Deleting Connections

1. Right-click a saved connection in the sidebar
2. Select Delete Connection
3. Confirm the deletion

Testing Connections

Before saving, click Test Connection to verify:

• Network connectivity to the server
• Authentication credentials are valid
• Selected database exists and is accessible

Object Explorer

Once connected, the Object Explorer shows your database structure:

Navigating the Tree

• Server - Top-level connection node showing server name
• Databases (or Schemas for Oracle) - List of databases/schemas on the server
• Tables - Database tables with column details
• Views - Database views
• Stored Procedures - Programmable database routines
• Functions - User-defined functions
• Packages, Sequences, Synonyms, DB Links, Materialized Views, Types, Directories - Oracle-specific object types

Object Actions

Right-click objects for context menu actions:

• Tables - Select Top 1000, Edit Top 200, Design Table, Script as CREATE/DROP
• Views - Select Top 1000, Script as CREATE/ALTER/DROP
• Procedures - Execute, Script as CREATE/ALTER/DROP
• Functions - Script as CREATE/ALTER/DROP

Troubleshooting

Connection Refused

• Verify the server address and port are correct
• Check that the database server is running
• Ensure firewall allows connections on the database port

SSMS connects but Jam doesn't (Windows local SQL Server)

• SSMS may be using Shared Memory / Named Pipes, while Jam’s direct Node driver connection uses TCP/IP. Jam retries some local connections via SQL Tools Service, but enabling TCP/IP for your instance in SQL Server Configuration Manager (and restarting SQL Server) is the most compatible setup.
• For named instances (e.g., localhost\\SQLEXPRESS), ensure the SQL Server Browser service is running (UDP 1434) or set the explicit TCP port in Jam.
• On Windows, Jam can retry MSSQL connections using SQL Tools Service when the direct driver connection fails, but driver-only features still require TCP/IP.

Authentication Failed

• Double-check username and password
• Verify the user has permission to connect
• For Windows Auth, ensure proper domain configuration

Oracle Connection Issues

• ORA-12541 (No Listener) - Verify the Oracle listener is running on the target host and port
• ORA-12514 (Service Not Found) - Check the service name is correct. Use lsnrctl status on the server to list available services
• ORA-01017 (Invalid Credentials) - Verify username and password. Oracle usernames are case-insensitive but passwords are case-sensitive
• TNS Alias Not Found - Ensure the TNS Admin directory path is correct and contains a valid tnsnames.ora file

Azure SQL Firewall

• Add your client IP address to the Azure SQL firewall rules
• Or enable "Allow Azure services" in the Azure portal