SQL Server
Excel

SQL Server to Excel Converter

SQL Server tables in a new .xlsx workbook, one sheet per table, with numbers and dates Excel can work with.

Version
5.8.0
Release Date
Nov. 8, 2026
Size
51.3 MB
Platform
Windows 10 or later

Rather not run it yourself?

Let us do the migration →

Export SQL Server tables into a new Excel workbook, one sheet per table. Numbers arrive as numbers, and dates as real Excel dates.

  • Reads the tables of a SQL Server database.
  • Writes an .xlsx workbook. No Microsoft Office or Excel driver is needed.
  • Runs on Windows as a desktop application.
  • The same download loads Excel into SQL Server. One licence key covers the MySQL and PostgreSQL pairs too.

What the workbook looks like

One sheet per table

Each sheet is named after its table. A name Excel cannot take, such as one over 31 characters, one with [ ] : * ? / \, or a duplicate, is changed to a valid one.

Column names in the first row

The rows follow underneath. A workbook holds tables, columns, and rows only.

A new file on every run

A workbook already at that path is replaced, and the application warns you before the run. Sheets are not added to an existing workbook.

A job keeps both connections, the table selection, and the options. Run it again from the application, or by name from Task Scheduler with --run-job.

How SQL Server values arrive in Excel

Scroll sideways to see all columns.

In SQL Server In the workbook What needs attention
Numbers Numbers. Excel keeps 15 significant digits. A longer number is written as text, every digit kept.
Dates and date-times Excel dates, with a date format applied.
Text Text. Excel holds 32,767 characters per cell. A longer value is refused by name, not cut.
NULL An empty cell.

Excel's row limit, and what stays in SQL Server

A sheet holds 1,048,575 data rows. A larger table is refused by name, never cut short. Keys, indexes, and constraints stay in SQL Server: a workbook has no place for them.

Supported versions and services

SQL Server

  • SQL Server 2008-2022, including Express editions
  • Azure SQL Database and Amazon RDS for SQL Server
  • SQL Server schemas (dbo, custom schemas)
  • Windows authentication or SQL authentication

Excel

  • Microsoft Excel workbooks (.xlsx)
  • No Microsoft Office or Excel driver needed

How to migrate SQL Server to Excel

1

Setup: connect SQL Server and Excel

Choose the source and destination connections side by side on one screen. A connection is saved once and reused by every job.

SQL Server source

Use the SQL Server connection guide.

Excel target

Name the .xlsx file to write. A workbook already at that path is replaced; the application warns before the run.

2

Tables & mapping: see every Excel type before a row moves

Pick the tables, then open one: each SQL Server column shows the Excel type it becomes. Change a type or a name in place; the line at the bottom names anything that would fail.

3

Execution: start it, and the job is saved

Review what the run will do, start it, and read the log as it goes. The job stays in the list to run again or put on a schedule.

Verify the copy

With Verify after the run on, the destination is checked when the copy ends: schema, totals and rows. The window shows which tables, rows and columns differ.

How Verify works

Every option, in the guide

Naming rules, table options, row filters, scheduling and the command line work the same for every database pair, so they live in one place.

Move SQL Server data into Excel

Download the current build and run the first job against your own database.

Windows Windows 10 or later · 51.3 MB