Database to Excel.
One Click Away.
Pull live database results directly into any Excel spreadsheet. No ODBC drivers, no VBA macros, no manual exports. Select a query, click Run, and watch your data appear.
Ask Nova, get SQL + charts
Meet Nova Database REST APIOne key per partner. No credentials shared.
Build an API AutomationScheduled sync to 6+ platforms
Explore API to SQLQuery APIs with SQL, no code
Explore AI Database MCPClaude, Cursor, ChatGPT & Grok talk to your data
Connect AIQuery Streams is a secure, real-time database integration platform that lets you pull live SQL results into Microsoft Excel and Google Sheets without configuring ODBC drivers, writing VBA macros, or sharing database credentials. Learn more at QueryStreams.com and sign up for free to start running data queries in Excel from any database in minutes.
The Challenge: Getting Database Data into Excel
Every team that works with data eventually faces the same problem: the data lives in a database, but the analysis happens in a spreadsheet. Whether it is a finance team building revenue forecasts, a sales team tracking pipeline metrics, or an operations team monitoring inventory levels, the destination is almost always Microsoft Excel. The challenge is getting that data from the database into Excel reliably, securely, and without turning it into a full-time job for your DBA.
Manual CSV Exports
Someone runs a query, exports to CSV, emails the file. By the time it arrives, the data is already stale.
Stale Snapshots
Scheduled exports and static files provide yesterday’s data at best. Decisions require current numbers, not last Tuesday’s report.
Credential Sharing
Giving Excel users database passwords creates security risks, audit problems, and zero visibility into who accessed what.
Complex Setup
ODBC drivers, DSN configurations, Power Query M-code, and VPN tunnels create friction that most spreadsheet users cannot manage alone.
The result is a bottleneck. Business users depend on IT or a DBA to extract data on their behalf, and each request becomes another ticket. According to Gartner, IT teams spend up to 40% of their time on ad-hoc data requests. The problem is not a lack of tools — it is that existing tools for running a data query in Excel either sacrifice security for convenience or sacrifice convenience for security.
Methods for Querying Databases from Excel
There are several established approaches for getting SQL data into an Excel spreadsheet. Each has trade-offs in complexity, security, and scalability. Understanding these options helps clarify why many teams are moving to agent-based solutions for using SQL in Excel.
ODBC / DSN Connections
The traditional method for connecting Excel to a database is through ODBC (Open Database Connectivity) drivers. You install a database-specific driver on each user’s machine, configure a DSN (Data Source Name) with the server address and credentials, then use Excel’s Data menu to import from the ODBC source. This approach works, but it requires IT to install and configure drivers on every workstation, embeds database credentials on each machine, and typically requires direct network access (VPN or firewall rules) to the database server. Maintenance becomes painful when server addresses change, passwords rotate, or driver versions need updating across dozens of machines.
Power Query (Get & Transform)
Power Query is built into modern versions of Excel and provides a visual interface for connecting to databases, transforming data, and loading results into worksheets. Power Query supports SQL Server, PostgreSQL, MySQL, Oracle, and other sources natively. It is more user-friendly than raw ODBC, but still requires users to understand connection strings, write or paste SQL queries, and have direct network access to the database. For enterprise environments where databases sit behind firewalls, Power Query hits the same network barriers as ODBC. It also stores connection details within the workbook, which creates credential management challenges when files are shared.
Copy-Paste and CSV Export
The most common approach in practice is also the least scalable: someone with database access runs a query in a SQL client (SQL Server Management Studio, pgAdmin, DBeaver, or similar), exports the results as a CSV file, and either emails it or drops it in a shared folder. The Excel user opens the CSV and works with the data. This method requires zero technical setup for the end user, but it produces stale data the moment the export completes, creates an ongoing dependency on the person running the queries, and offers no audit trail or access controls. For a one-time data pull, it works fine. For recurring reports that need fresh data, it does not scale.
Query Streams: Agent-Based Live Data
Query Streams takes a fundamentally different approach. Instead of requiring Excel users to connect directly to your database, a lightweight network Agent runs on any machine with database access and creates an outbound-only WebSocket connection to the cloud relay. A DBA or data team builds saved queries in the web portal, then shares them with specific users. Those users open the Query Streams add-in inside Excel, pick a query from a dropdown, optionally adjust filters, and click Run. Live results stream directly into the worksheet. No ODBC drivers, no Power Query connection strings, no VBA scripts, no database credentials anywhere near the spreadsheet.
How Query Streams Works as an Excel Data Query Tool
Setting up Query Streams for Excel data queries involves four steps. Once configured, your team gets unlimited on-demand access to live database results without any ongoing IT involvement.
Install the Agent
Download the Query Streams Agent onto any Windows, Linux, or macOS machine that can reach your database. The Agent connects outbound only — no firewall changes needed.
Build Saved Queries
Write SQL in the web portal targeting SQL Server, PostgreSQL, MySQL, MariaDB, Oracle, BigQuery, Snowflake, SQLite, DuckDB, or Access. Add interactive filters for common parameters.
Share with Excel Users
Grant per-user or per-team access to specific queries. Users see only query names and descriptions in the Excel add-in — never the SQL, table names, or credentials.
Run from Excel
Users open the add-in, pick a query from their dropdown list, set any filters, and click Run. Live results stream into the active worksheet instantly.
The Agent supports connections to 10+ databases from a single installation — Microsoft SQL Server (including Azure SQL Database and AWS RDS), PostgreSQL (including Google Cloud SQL), MySQL, MariaDB, Oracle, Snowflake, Google BigQuery, SQLite, DuckDB, and Microsoft Access. Multiple agents can be deployed across your entire infrastructure (on-premises data centers, AWS EC2, Azure VMs, Google Cloud), and all their data sources appear as a single unified dropdown in the query builder. Users simply select from available data sources without needing to know which agent or physical location hosts the database. For optimal performance, deploy agents in the same network or region as their databases.
Interactive Filters: Let Users Customize Queries Without SQL
One of the most powerful features for running data queries in Excel is Query Streams’ interactive filter system. Instead of building dozens of nearly identical queries for different date ranges, regions, or departments, a DBA builds a single query with configurable parameters. End users then adjust those parameters from the Excel add-in without ever touching the SQL.
Query Streams supports two approaches to filter creation. You can use explicit SQL variables (e.g., @start_date, @region, @department) that become named filter fields in the add-in. Alternatively, Query Streams can auto-detect static values in your WHERE clauses — for example, if your query includes WHERE region = 'Northeast', the platform detects Northeast as a filterable value. You enable this from the query’s Properties tab, where a Config switch can be toggled for any detected filter. Users see clean dropdowns, date pickers, or text fields in Excel and adjust them freely before each execution.
Explicit Variables
Use @parameter_name syntax in your SQL. Each variable becomes a named filter field in the Excel add-in with the data type you specify.
Auto-Detected Filters
Query Streams scans your WHERE clauses for static values and offers them as configurable filters. Enable any with a toggle in the Properties tab.
Zero SQL Exposure
Excel users see friendly filter names and dropdowns. They never see the underlying SQL, table names, or schema — just the parameters you expose.
This capability is what sets Query Streams apart from other methods of using SQL in Excel. With ODBC or Power Query, each user either writes their own SQL or receives a static query with no flexibility. With Query Streams, a single query serves an entire team — each person adjusts the filters independently to get exactly the data they need, on demand, without submitting a ticket or waiting for a new CSV export.
Parallel Execution: Refresh Multiple Queries Simultaneously
A common limitation of traditional database-to-Excel workflows is serial execution. With ODBC or Power Query, refreshing multiple data connections usually happens one at a time — you wait for query A to finish before query B starts. For teams that need to populate multiple worksheet tabs with different datasets, this sequential approach wastes significant time.
Query Streams supports parallel query execution. Users can launch five or more saved queries simultaneously into different worksheet tabs, and the Agent streams each result set concurrently, regardless of result size. A finance team refreshing five different reports — revenue by region, expense breakdown, headcount projections, pipeline summary, and budget variance — can kick them all off at once. Each query runs independently on the Agent, and data streams back to each tab as soon as it is ready.
Comparison: ODBC vs Power Query vs Query Streams for Excel Data Queries
The following table compares the three primary methods for pulling SQL into Excel across the factors that matter most for enterprise and team use. Whether you need to connect a local SQL Server, a remote PostgreSQL instance on AWS RDS, or a cloud-hosted Snowflake warehouse, each approach has distinct strengths and weaknesses.
| Capability | ODBC / DSN | Power Query | Query Streams |
|---|---|---|---|
| Setup per user | Driver install + DSN config | Connection string + SQL paste | Install Excel add-in (one-time) |
| SQL knowledge in Excel | Required | Required or pasted | Not needed — select from dropdown |
| Live, on-demand data | Yes | Yes | Yes |
| Credential security | Stored on each machine | Stored in workbook | Stays on Agent server only |
| Network requirement | Direct / VPN to database | Direct / VPN to database | Internet only (outbound Agent) |
| Interactive filters | Manual SQL editing | Parameters possible but complex | Built-in dropdowns and date pickers |
| Parallel execution | Sequential refresh | Limited by connection | 5+ queries simultaneously |
| Share queries with team | Share workbook or SQL files | Share workbook | Per-user sharing with access control |
| SQL visible to user | Yes — fully exposed | Yes — in query editor | No — hidden by design |
| Audit trail | None | None | Full execution log per user |
| Database support | Varies by driver | ~8 native connectors | 10+ (SQL Server, PostgreSQL, MySQL, MariaDB, Oracle, Snowflake, BigQuery, SQLite, DuckDB, Access) |
| Works in Google Sheets | No | No | Yes — same queries, same add-on |
For individual power users who are comfortable with SQL and have direct network access, ODBC and Power Query remain viable options. For teams — where a DBA needs to provide controlled, secure, self-service data access to non-technical Excel users across different networks — Query Streams eliminates the setup complexity, credential risks, and ongoing maintenance that traditional methods require.
Security: No Credentials in Excel, No Inbound Firewall Rules
The security implications of running data queries from Excel are often overlooked until there is an incident. When ODBC connections or Power Query store database credentials inside workbooks or DSN configurations on user machines, every shared spreadsheet and every laptop becomes a potential credential leak. Query Streams eliminates this attack surface entirely.
-
Credentials on every machine
ODBC DSN entries and Power Query connections store usernames and passwords on each user’s workstation.
-
Credentials in shared files
When workbooks with embedded connections are shared, database passwords travel with them.
-
Direct network exposure
Users need VPN access or direct connectivity to the database server, requiring inbound firewall rules or port forwarding.
-
No execution audit
No centralized log of who ran which query, when, or with what parameters.
-
Zero credentials in Excel
Database passwords stay exclusively on the Agent server. Nothing is stored in the add-in, workbook, or user’s machine.
-
Shareable without risk
Workbooks contain only data results, not connections. Sharing a file does not expose any credentials or access paths.
-
Outbound-only Agent
The Agent initiates all connections outward on standard HTTPS/WSS ports. No inbound rules, no VPN, no open ports.
-
Full execution logging
Every query run is logged with user identity, timestamp, filter parameters, and result metadata for audit compliance.
Works with Google Sheets Too
Not everyone on your team uses Microsoft Excel. Query Streams also provides a Google Sheets add-on that works with the same saved queries, the same interactive filters, and the same Agent infrastructure. A DBA builds a query once in the web portal, and that query is available in both the Excel add-in and the Google Sheets add-on simultaneously. A shared user can independently select a query from their list, adjust any available filters, and run it to get live data on demand from either platform — without any action needed from the query creator.
This cross-platform compatibility means your team is not locked into a single spreadsheet tool. Finance might prefer Excel for its pivot table capabilities, while marketing might prefer Google Sheets for real-time collaboration. Both access the same live database data through the same secure pipeline. Query Streams supports parallel query execution in both Excel and Google Sheets — users can launch multiple queries into different worksheet tabs simultaneously and the Agent streams each concurrently, regardless of result size.
Frequently Asked Questions
What is a data query in Excel? +
Do I need to know SQL to use Query Streams in Excel? +
How is Query Streams different from ODBC or Power Query? +
Which databases can I query from Excel using Query Streams? +
Can I run multiple queries into different Excel tabs at the same time? +
Is my database exposed to the internet when using Query Streams? +
How do interactive filters work in the Excel add-in? +
@start_date, @region) or let Query Streams auto-detect static values in WHERE clauses. In the Excel add-in, these filters appear as dropdowns, date pickers, or text fields. Each user adjusts filters independently before clicking Run — they get customized results from a single shared query without editing any SQL. Filters are configured in the query’s Properties tab in the web portal.Can a DBA share queries with users who have no database knowledge? +
Does Query Streams work with Excel Online, Office 365, and desktop Excel? +
How do I get started with data queries in Excel using Query Streams? +
Get Started
Pull Live Data into Excel in Minutes
Stop exporting CSVs and managing ODBC drivers. Deploy a secure Agent, build your first saved query, and let your team pull live database results from Excel with one click. Free tier available — no credit card required.
Related guides: Download the Query Streams Agent | Databases in Microsoft Excel | Databases in Google Sheets | AI Data Analytics with Nova | How to Run SQL Queries in Excel
Category: Articles
Tags: data query in excel, sql in excel, database to excel, excel database connection, live data excel, sql into excel, Excel add-in, database query spreadsheet, query streams, Excel data import
Meta Description: Pull live database results into Excel instantly. No ODBC, no VBA — just select a query and run.

