Convert MySQL to SQL Server.

DBConvert/ DBSync software automates conversion and synchronization of your data from MySQL to Microsoft SQL Server. Transfer the entire database or select only needed dataset at customization stage in easy-to-use wizard style GUI.

Views migration between MS SQL Server and MySQL in both directions is possible. You don’t need to know any differences in SQL syntax. Every view will be converted from source db to target automatically.

Integrated Data Types Mapping feature helps to find and map similar data types between MySQL/ MariaDB and MS SQL Server to make cross database conversion more flexible. Read more info about Data types mapping between MySQL and MS SQL Server.

So if you decided to choosing Microsoft SQL Server as a back-end for your application or need to replicate/ synchronize data between MySQL and MS SQL DBMS, here you can find solutions for automating your migration jobs.

There is an option to put the result into a dump file instead of transferring it directly to another MS SQL database.

Trigger-based synchronization method helps increase the speed of data comparing and replication significantly.

Use built-in Scheduler to automatically launch the conversion and synchronization tasks.

 DBConvert for MSSQL & MySQL

Migration directions:

  • SQL Server → MySQL | MariaDB | Percona
  • MySQL | MariaDB | Percona → SQL Server
  • SQL Servet ↔ Azure Database for MySQL
  • SQL Azure ↔ MySQL | MariaDB | Percona | SQL Server
  • SQL Server ↔ Amazon RDS | Aurora ↔ MySQL
  • ☑ Views conversion between SQL Server and MySQL/ MariaDB
  • SQL Server ↔ Google Cloud ↔ MySQL
  • MSSQL ↔ MySQL Dump, PHP Script
  • MySQL ↔ SQL Azure, SQL Server Dump

Version: 4.2.7

Release Date: Oct. 3, 2018

 DBSync for MSSQL & MySQL

Sync directions:

  • SQL Server ↔ MySQL ↔ MariaDB | Percona
  • MySQL ↔ SQL Azure | Aurora ↔ MariaDB
  • SQL Server ↔ Amazon RDS | Aurora ↔ MySQL
  • SQL Server ↔ Google Cloud ↔ MySQL

Version: 5.4.3

Release Date: Oct. 3, 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

Using MySQL 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 MySQL source database.

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

Connect to MySQL 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:

  • MySQL to SQL Server
  • SQL Server to MySQL
  • MySQL to MySQL
  • SQL Server to SQL Server

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 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 MySQL to SQL Server.

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 MySQL database to the closest equivalent of the target SQL Server 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 MySQL 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 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, 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

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)