Skip to main content
Queryly supports multiple database providers, allowing you to work with different database systems using a consistent interface. Each provider implements connection management, schema exploration, query execution, and data export capabilities.

​
Supported Database Types

Queryly currently supports four major database systems:

SQLite

Lightweight, file-based database perfect for local development

PostgreSQL

Powerful, open-source relational database system

MySQL

Popular open-source relational database

SQL Server

Microsoft’s enterprise-grade database system

​
Feature Comparison

All providers support the core Queryly features:
FeatureSQLitePostgreSQLMySQLSQL Server
Connection Management
Schema Exploration
Table Browsing
Query Execution
Data Export (CSV/JSON)
Schema SupportN/APublic onlyN/A
File-based
Network Connection

​
Connection String Anatomy

Each database provider uses a specific connection string format:

​
SQLite

Data Source=path/to/database.db
Simple file path pointing to your SQLite database file.

​
PostgreSQL

Host=localhost;Database=mydb;Username=user;Password=pass
Requires host, database name, and credentials.

​
MySQL

Server=localhost;Database=mydb;User=root;Password=pass
Similar to PostgreSQL but uses Server and User keywords.

​
SQL Server

Server=localhost;Database=mydb;User Id=sa;Password=pass;TrustServerCertificate=True
Includes TrustServerCertificate for SSL handling.

​
Choosing the Right Provider

  • Local development - Perfect for prototyping and testing
  • Single-user applications - No concurrent write issues
  • Embedded databases - No server setup required
  • Small to medium datasets - Efficient for datasets under 1GB
  • File-based portability - Easy to copy and share
  • Production applications - Battle-tested and reliable
  • Complex queries - Advanced SQL features and performance
  • JSON/JSONB support - First-class JSON storage
  • Multi-user environments - Excellent concurrency handling
  • Data integrity - Strong ACID compliance
  • Web applications - Popular LAMP/LEMP stack choice
  • Read-heavy workloads - Optimized for read operations
  • High availability - Robust replication features
  • Large user bases - Proven scalability
  • WordPress/PHP apps - Industry standard pairing
  • Windows environments - Native Windows integration
  • Enterprise applications - Enterprise-grade features
  • .NET integration - Seamless .NET ecosystem support
  • Advanced features - Full-text search, spatial data
  • Microsoft stack - Azure, Active Directory integration

​
Adding a Connection

Regardless of the provider, adding a connection follows the same workflow: 
queryly connect add
You’ll be prompted for:
  1. Connection name - A friendly name (e.g., “LocalDB”, “ProductionDB”)
  2. Database type - Select from SQLite, PostgreSQL, MySQL, or SQL Server
  3. Connection string - Provider-specific connection string
The connection is automatically tested before being saved.
Connection strings are stored in ~/.queryly/connections.json. Ensure this file has appropriate permissions to protect sensitive credentials.

​
Testing Connections

After adding a connection, you can test it anytime: 
queryly connect test MyConnection
This verifies:
  • Connection string is valid
  • Database is accessible
  • Credentials are correct
  • Network connectivity (for remote databases)

​
Common Connection Parameters

​
Timeout Settings

Most providers support timeout parameters:
  • SQLite: Default Timeout=30
  • PostgreSQL: Timeout=30;Command Timeout=30
  • MySQL: Connection Timeout=30;Default Command Timeout=30
  • SQL Server: Connection Timeout=30;Command Timeout=30

​
SSL/TLS Configuration

Secure connections for network databases:
  • PostgreSQL: SSL Mode=Require or SSL Mode=Prefer
  • MySQL: SslMode=Required or SslMode=Preferred
  • SQL Server: Encrypt=True;TrustServerCertificate=False

​
Connection Pooling

All providers support connection pooling:
  • SQLite: Limited pooling support
  • PostgreSQL: Pooling=true;Minimum Pool Size=0;Maximum Pool Size=100
  • MySQL: Pooling=true;MinimumPoolSize=0;MaximumPoolSize=100
  • SQL Server: Pooling=true;Min Pool Size=0;Max Pool Size=100

​
Next Steps

SQLite Setup

Learn how to configure SQLite connections

PostgreSQL Setup

Connect to PostgreSQL databases

MySQL Setup

Configure MySQL connections

SQL Server Setup

Set up SQL Server connections

​
Troubleshooting

If connection tests fail, verify:
  • Connection string format matches the provider syntax
  • Database server is running (for network databases)
  • Firewall allows connections on the database port
  • Credentials are correct and have appropriate permissions
  • For file-based databases (SQLite), the file path is correct and accessible
For provider-specific troubleshooting, see the individual provider documentation pages.

Build docs developers (and LLMs) love

Get started for freeTalk to us