Convert Excel to SQL Server.

DBConvert for MS Excel and MSSQL is an application designed to convert Microsoft Excel/ CSV to Microsoft SQL Server / Windows Azure SQL databases and vice versa. The built-in data selector helps simplify choosing data ranges in .xls / .xlsx.

Set up your data source by selecting either the entire Excel workbook or individual data ranges from an MS Excel spreadsheet or CSV file. See List of available migration directions supported by DBConvert for Excel and MS SQL. The software is also suitable for database migration between two SQL servers / Windows Azure SQL databases or even two Excel files.

Supported databases:
  • Microsoft Excel
  • CSV
  • Microsoft SQL Server
  • Microsoft SQL Dump
  • Amazon RDS
  • Amazon Aurora
  • Azure Database for MySQL
  • Google Cloud SQL for MySQL
 DBConvert for Excel & MSSQL

Version: 1.4.5

Release Date: April 12, 2023

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

DBConvert Studio

 Version: 3.4.4

Release Date: Sept. 16, 2023

Supported databases:

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

Using Excel to SQL Server 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 Excel source database.

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

Connect to Excel source database from DBConvert

2. Connect to SQL Server 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 SQL Server 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:

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

NOTE #2: Don't be confused by the fact that connections to cloud databases like Amazon RDS, 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. Configure database migration options.

At the next step, you can specify precisely which tables, fields, indices, views you want to transfer to the SQL Server 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 Excel to SQL Server.

Check out our articles about Configure database migration options. 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.

By default, DBConvert tries to automatically map the database types of the source Excel database to the closest equivalent of the target SQL Server database types. However, you can manually change the data types for the entire database globally using the "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 Excel to SQL Server

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 Excel source and SQL Server 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.

Find more Information about built-in scheduler

DBConvert screenshot

Supported OS:

Requirements

  • Microsoft Visual C++ 2008 x86 Redistributable package
  • Necessary privileges to write into network shared folder (LAN or VPN) where destination database Excel resides
  • 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)

Related Links

Highlights

Read information about reverse migration.