Convert SQL Server to Excel.

Convert database from SQL, Azure to Excel

To simplify the process of data migration from a Microsoft SQL Server or Windows Azure SQL databases to Excel spreadsheets (.xls and .xlsx formats) and vice versa, our DBConvert for Excel and MSSQL is the perfect solution.

In most cases Excel data would be consolidated to a MS SQL Server database. But in some situations there would be a business need to distribute part of the data in opposite direction from MSSQL to Excel spreadsheets.

Before creating your destination Excel data, you can visualize it in the configurable tree-view and change it using a large number of customizable settings. The application gives you an opportunity to filter the MSSQL source data needing to be transferred.

You can move your data just in few easy steps. The user interface is very user-friendly, streamlined and very simple to use.

All data transfers can be scheduled such that database migrations will happen automatically.

 DBConvert for Excel & MSSQL

Migration directions:

  • Excel → MS SQL Server, MS SQL Dump
  • MS SQL Server → Excel, MS SQL Dump
  • Excel ↔ Amazon RDS

Version: 1.4.2

Release Date: Feb. 21, 2018

Try All-in-one DB migration and Sync software.

DBConvert Studio

 Version: 1.8.2

Release Date: Sept. 17, 2020

Supported databases:

  • SQL Server
  • MySQL
  • Oracle
  • PostgreSQL
  • Access
  • FoxPro
  • SQLite
  • Firebird
  • Excel
  • IBM DB2
  • Azure SQL
  • Amazon RDS
  • Amazon Aurora
  • Heroku Postgres
  • Google Cloud

Related Links

Supported OS:

Using SQL Server to Excel conversion and synchronization tools.

When you start DBConvert or DBSync application in GUI mode it guides you through several steps to set up the database migration or synchronization:

1. Connect to SQL Server source database.

If a source database requires you to log in, you can specify a user name/ password and host/ port parameters.

Connect to SQL Server source database from DBConvert

2. Connect to Excel destination database.

Specifying parameters for destination database looks like the same as for source. Usually, it consists of defining connection settings and username/password pairs.

Connect to Excel target database from DBConvert

NOTE #1: Every DBConvert or DBSync tool has two different databases in its name. That means any specified database from a pair can be set up as a source or destination. Besides, the same type of database may be set up both as a source or destination.

As an example, here is the list of possible migration directions with on-premises databases:

  • SQL Server to Excel
  • Excel to SQL Server
  • SQL Server to SQL Server
  • Excel to Excel

NOTE #2: Don't be confused by the fact that connections to cloud databases like Amazon RDS, Microsoft Azure SQL, Google Cloud, and Heroku are not explicitly specified in the configuration of a source or destination in the DBConvert / DBSync interface. To connect to Cloud database instances, use the same settings as you do for traditional on-premises databases.

NOTE #3: Your connections to source and target databases stay active until you close DBConvert/ DBSync application or reopen new connections on "source" and "destination" steps.

Read more about the specific source/ destination configurations for different databases.

3. Custoimzation and configuration.

At the next step, you can specify precisely which tables, fields, indices, views you want to transfer to the Excel destination database. Just check/ uncheck the box in front of each database object you want to convert.

Customize general database/ tables settings. Or set up a particular table , field, index individually when migrating data from SQL Server to Excel.

Check out our articles about Custoimzation and configuration. for detailed information.

The screenshot below sums up general features available in DBConvert software solutions.

4. Detection of potential database migration issues. Errors and Warnings

The database typically constrains certain relations on the data that cannot be violated. On the customization step, a smart error checker verifies all possible Data integrity and Referential integrity issues and highlights them, if any, before performing a migration.

DBConvert software to default tries to automatically map database types from the source SQL Server database to the closest equivalent of the target Excel database types. But you can manually change data types for the whole database globally with "Global mapping" or individually for each field.

Check out Smart error checker. Errors and Warnings for more information.

5. Execution. The final stage of data migration from SQL Server to Excel

Once you configure source and destination databases for migration in the previous steps, you can start the actual conversion or synchronization process.

Click the "Commit" button to start conversion. Also, here, you can monitor the migtation/ synchronization process.

Optionally save connection settings and configuration parameters into the session file to schedule the launching of sync or migration jobs regularly.

Execution step of DBConvert products

Read more about execution stage available options.

Command line mode

Previously saved sessions can be passed as parameters to Command-Line DBConvert Client. A session keeps SQL Server source and Excel target database connection settings with other specified options.

Example: C:\Program Files\DBConvert\excel2mssqlPro\excel2mssqlPro_Cons.exe /Session:"Session_Name"

NOTE: First, you have to run the software in GUI mode to create a session file with initial parameters.

Built-in scheduler.

Our applications come with a built-in scheduler to run database migration and sync jobs at specified times. Just set the scheduled date and time to execute job sessions automatically.

DBConvert screenshot

Highlights

  • Saving data into a SQL Dump for export to SQL Server database
  • Ability to create tables from MS Excel file with Integrated Data Selector
  • Amazon RDS SQL Server DB Instance support
  • Microsoft Excel 2000 or higher 2003/2007/2010/2013/2016
  • Bi-directional synchronization between SQL Server, MySQL, Oracle and PostgreSQL
  • Views conversion from SQL Server to MySQL and Oracle and back support
  • MS SQL Server (Express) 2000/2005/2008/2008 R2/2012/2014/2016, Azure SQL support
  • SQL Server schemes support
  • Speed up conversion with Bulk and Quantization features.
  • Connect to SQL Server either TCP/IP, PIPE or IPX/SPX communication protocol

Requirements

  • Necessary privileges to write into database on the target SQL Server (this requirement is optional as there is an option to overcome the restrictions using dump file)
  • Necessary privileges to write into network shared folder (LAN or VPN) where destination database Excel resides
  • Microsoft Visual C++ 2008 x86 Redistributable package