Excel SQL Database Integration: Connect Excel to SQL Server, MySQL and PostgreSQL

What Is Excel SQL Database Integration?

• Databases: SQL Server, Azure SQL, MySQL, PostgreSQL, Oracle and anything with an ODBC or OLE DB driver.

• Tools: Power Query (Get Data), ODBC and OLE DB connections, the Data Model, and VBA with ADO.

• Refresh: on file open, on a timer, by button or macro, or scheduled outside Excel.

• Security: Windows Authentication, read-only logins, access to views instead of base tables, encrypted connections.

• Pricing: fixed-scope quote after a free review. Projects typically start at $1,200.

How to Connect Excel to a SQL Database (Step by Step)

1. Open the SQL Server connector. In Excel, go to Data > Get Data > From Database > From SQL Server Database.
2. Enter the server and database. Type the server name (for example SQLPROD01 or SQLPROD01\SQLEXPRESS) and, optionally, the database name. Leave Import selected.
3. Choose authentication. Use Windows authentication when your domain account has access, or Database authentication with a read-only SQL login. Accept the encrypted connection prompt.
4. Select a table or view. In the Navigator, choose the table or view, preferably a reporting view, then select Transform Data to filter columns and rows or Load to import it.
5. Set the refresh behavior. Open Data > Queries & Connections, right-click the query, choose Properties, and enable Refresh data when opening the file or Refresh every N minutes.

That gets a table into Excel. For a report people rely on, we go further: connect to a purpose-built SQL view, filter on the server with a parameter, and load only the columns you need. In Power Query M that looks like this:

let
    // StartDate is a Power Query parameter (Home > Manage Parameters)
    Source   = Sql.Database("SQLPROD01", "Sales", [CommandTimeout = #duration(0, 0, 5, 0)]),
    Orders   = Source{[Schema = "dbo", Item = "vw_OrdersForExcel"]}[Data],
    // This filter folds to a WHERE clause, so SQL Server does the work, not Excel
    Filtered = Table.SelectRows(Orders, each [OrderDate] >= StartDate),
    Selected = Table.SelectColumns(Filtered, {"OrderID", "OrderDate", "CustomerName", "Total"})
in
    Selected

Because the filter folds back to SQL Server as a WHERE clause, Excel downloads only the rows it needs and refreshes stay fast even on large tables.

Power Query vs ODBC vs VBA: Which Connection Method Should You Use?

Example: parameterized SQL query from Excel VBA

When users need date pickers, a refresh button or write-back, we use ADO with parameters. Parameters prevent SQL injection and let SQL Server reuse execution plans. This version uses Windows Authentication, an encrypted connection and guaranteed cleanup:

Option Explicit

' Pulls parameterized SQL Server data into the "Data" sheet.
' Uses late binding, so no extra VBA references are required.
' Requires Microsoft ODBC Driver 17 or 18 for SQL Server on the user's PC.

Public Sub RefreshSalesFromSql()
    Dim cn As Object, cmd As Object, rs As Object
    Dim ws As Worksheet, i As Long
    Dim startDate As Date, endDate As Date

    Set ws = ThisWorkbook.Worksheets("Data")
    startDate = ThisWorkbook.Worksheets("Controls").Range("StartDate").Value
    endDate = ThisWorkbook.Worksheets("Controls").Range("EndDate").Value

    On Error GoTo Fail
    Application.ScreenUpdating = False

    Set cn = CreateObject("ADODB.Connection")
    cn.ConnectionString = "Driver={ODBC Driver 18 for SQL Server};" & _
        "Server=SQLPROD01;Database=Sales;Trusted_Connection=Yes;" & _
        "Encrypt=Yes;TrustServerCertificate=No;"
    cn.CommandTimeout = 120
    cn.Open

    Set cmd = CreateObject("ADODB.Command")
    With cmd
        .ActiveConnection = cn
        .CommandType = 1   ' adCmdText
        .CommandText = "SELECT OrderID, OrderDate, CustomerName, Total " & _
                       "FROM dbo.vw_OrdersForExcel WHERE OrderDate >= ? AND OrderDate < ?"
        .Parameters.Append .CreateParameter("startDate", 135, 1, , startDate)  ' adDBTimeStamp, adParamInput
        .Parameters.Append .CreateParameter("endDate", 135, 1, , endDate)
        Set rs = .Execute
    End With

    ws.Rows("2:" & ws.Rows.Count).ClearContents
    For i = 0 To rs.Fields.Count - 1
        ws.Cells(1, i + 1).Value = rs.Fields(i).Name
    Next i
    ws.Range("A2").CopyFromRecordset rs

Cleanup:
    On Error Resume Next
    If Not rs Is Nothing Then rs.Close
    If Not cn Is Nothing Then cn.Close
    Application.ScreenUpdating = True
    Exit Sub
Fail:
    MsgBox "SQL refresh failed: " & Err.Description, vbExclamation
    Resume Cleanup
End Sub

Connecting Excel to SQL Server, MySQL, PostgreSQL and Oracle

Common Excel SQL Integration Use Cases

• Finance: transaction, AR/AP and general ledger extracts that refresh for month-end instead of being rebuilt.

• Sales: territory, pipeline and quota reports from a CRM or order database.

• Operations: inventory, production and fulfillment tracking from an ERP or warehouse system.

• Management: self-service dashboards so leaders do not wait on IT for each new export.

• Analysts: ad-hoc queries run safely inside Excel against approved views.

• Compliance: reports that always run the same approved query, with a clear source of truth for auditors.

Common Excel to SQL Connection Errors and How We Fix Them

What's Included in Our Excel SQL Integration Services

• Requirements analysis: data sources, refresh frequency, users and security needs

• Database connectivity setup and testing, including ODBC and OLE DB drivers

• Power Query connections with query folding and parameters

• Purpose-built SQL views or stored procedures for reporting

• VBA and ADO automation for parameter forms, refresh buttons and controlled write-back

• Query optimization and indexing recommendations

• Scheduled and on-open refresh automation

• Data transformation, cleaning and validation logic

• Error handling, connection recovery and refresh logging

• Access control, documentation, user training and ongoing support

How Much Does Excel SQL Database Integration Cost?

Is Excel still the right tool?

Sometimes the better answer is to move the data itself. If several people edit the same workbook or the file keeps growing, consider moving the workbook to a database. If your data lives in Access, you can move the tables to SQL Server and keep the Access screens, then point Excel at the same SQL Server. We will tell you honestly which route fits during the free review. If your source is an application rather than a database, see our API integration with MS Access and Excel service.

Last updated: October 6, 2026. Reviewed by the Excel Access Expert engineering team.