MySQL to SQL Server conversion and synchronization.

DBConvert / DBSync software automates the conversion and synchronization of your data from MySQL to Microsoft SQL Server and vice versa. Migrate the entire database, or select only the dataset you need during the configuration pass in a user-friendly wizard-style GUI.

At the core level, both MySQL and Microsoft SQL Server have a lot in common. The reason for migrating or syncing data depends on your business needs, available budget, and environment.

Microsoft SQL Server Migration Assistant for MySQL performs the tasks of migrating MySQL to SQL Server. But with SSMA, you can only transfer data in ONE direction to MSSQL. Also, it does not perform tasks such as synchronization between MySQL and MS SQL Server.

Why use DBconvert tools?

  1. DBConvert and DBSync for MySQL and MS SQL perform database conversion and synchronization tasks between the following databases in any direction:
    • Microsoft SQL Server,
    • MariaDB,
    • Percona,
    • Windows Azure SQL Databases/ Azure SQL Data Warehouse,
    • Azure Database for MySQL,
    • AWS RDS/ Aurora,
    • Google Cloud SQL for SQL Server,
    • Google Cloud SQL for MySQL.
  2. Data types in MS SQL and MySQL are similar but not the same. The Type Mapping feature helps you map MySQL data types to their closest and relative SQL Server equivalents.
  3. Parallel migration engine of DBConvert takes full advantage of modern multi-core processors. It speeds up data migration by splitting database tables into multiple parts and processing them in parallel.
  4. You don't need to know how to write scripts to convert views from MySQL to SQL Server. DBConvert will convert every selected view automatically.

Database synchronization between MySQL and SQL Server.

After copying your data from source MySQL to the target SQL Server, you would need to sync your data. DBSync software keeps your databases totally in sync with Update, Insert, and Drop synchronization types.

Trigger-based synchronization algorithm instantly tracks changes in both source and destination databases. The trigger-based sync method increases recurrent synchronization speed in times.

Bi-directional synchronization helps to update data in both MySQL and MSSQL databases simultaneously.

Supported databases:
  • SQL Server
  • MySQL
  • MariaDB
  • SingleStore DB (formerly MemSQL)
  • TiDB
  • Percona Server for MySQL
  • Vitess
  • Azure Database for MySQL
  • SQL Azure
  • Amazon RDS
  • Amazon Aurora
  • Google Cloud
  • ☑ Views conversion between SQL Server and MySQL
  • MySQL Dump
  • PHP Script
  • SQL Server Dump
 DBConvert for MSSQL & MySQL

Version: 4.3.2

Release Date: Oct. 24, 2023

 DBSync for MSSQL & MySQL

Version: 5.4.9

Release Date: May 22, 2024

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

DBConvert Studio

 Version: 4.0.8

Release Date: June 6, 2024

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 MySQL to SQL Server conversion and synchronization tools.

When launching the DBConvert or DBSync application in GUI mode, it seamlessly guides you through the steps to initiate database migration or synchronization:

1. Connect to MySQL source database.

Specify the username/password and host/port parameters if your source database requires login credentials.

Connect to MySQL source database from DBConvert

2. Connect to SQL Server destination database.

Specify parameters for the destination database similar to the source, defining connection settings and username/password pairs.

Connect to SQL Server target database from DBConvert

NOTE #1: Each DBConvert or DBSync tool's name comprises two different databases, enabling any specified database to operate as the source or destination. Furthermore, the same type of database can function as both the source and destination.

NOTE #2: Connections to cloud databases (e.g., Amazon RDS, Google Cloud, or Azure SQL) aren't explicitly specified in the user interface but use the same settings as traditional on-premises databases.

NOTE #3: Connections to source and target databases remain active until you close the DBConvert/DBSync application or reopen new connections.

Refer to our documentation for specific source/ destination configurations for different databases.

3. Configure database migration options.

Specify the tables, fields, indices, and views you want to transfer to the SQL Server destination database by checking/unchecking the corresponding boxes.

Customize general database/ tables settings. Or configure specific table , field, index object individually when migrating data.

Explore our articles in the user's manual about Configuring database migration options. for detailed information.

The screenshot below summarizes the general features available in DBConvert software.

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

The database enforces certain relations on the data, and on the customization step, an intelligent error checker verifies all possible data integrity and referential integrity issues. It highlights any problems before migration starts.

By default, DBConvert attempts to automatically map the database types of the source MySQL 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.

Explore the Intelligent error checker for more information. on errors and warnings

5. Execution. The final stage of data migration.

Initiate the conversion or synchronization process after configuring source and destination databases in the previous steps.

Click the "Commit" button to start conversion. Here, you can also monitor the migration/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

Explore more about the options available during the execution stage

Command line mode

Pass previously saved sessions as parameters to the Command-Line DBConvert Client. A session retains MySQL source and SQL Server target database connection settings with other specified options.

Example:

C:\Program Files\DBConvert\mssql2mysqlPro\mssql2mysqlPro_Cons.exe /Session:"Session_Name"

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

Built-in scheduler.

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

Find more Information about the built-in scheduler

DBConvert screenshot

Supported OS:

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 database on the target MySQL server (this requirement is optional as there is an option to overcome the restrictions using dump file or PHP Script)

Highlights

Explore details regarding reverse migration.