Migrating data from MySQL to SQL Azure

This guide walks you through migrating data from MySQL to SQL Azure in a few simple steps using ESF Database Migration Toolkit. Simplify complex migration tasks and save valuable time with our streamlined approach.

MySQL vs. SQL Azure:

MySQL is an open-source relational database management system (RDBMS) that provides a powerful and scalable platform for managing and storing data. Developed by Oracle Corporation, MySQL is widely used in web applications and is known for its reliability, flexibility, and ease of use. It supports various storage engines, including InnoDB for transactional processing and MyISAM for read-intensive applications, offering developers the flexibility to choose the engine that best suits their needs. With features like ACID compliance, replication support, and a thriving community of developers, MySQL is a popular choice for businesses of all sizes looking to build robust and efficient database-driven applications.
Microsoft SQL Azure, also known as Azure SQL Database, is a fully managed relational database service provided by Microsoft. It offers scalable and high-performance SQL database capabilities in the cloud, with built-in high availability, automated backups, and robust security features. Designed to handle both small and large-scale applications, Azure SQL Database simplifies database management tasks, allowing developers to focus on building applications without worrying about underlying infrastructure. It supports various deployment options, including single databases, elastic pools, and managed instances, catering to diverse business needs.

Prerequisite:

Software Required:

DMToolkit_x64.zip (63.5 MiB)	64-bit Windows application for ESF Database Migration Toolkit 12.2.07 (2025-07-01). (md5: 0750355677f7108916a6c1f2bc0d4d87)
DMToolkit_win32.zip (58.9 MiB)	32-bit Windows application for ESF Database Migration Toolkit 12.2.07 (2025-07-01). (md5: a9ba6351d787ff958b4ff2d9ca888576)

System Supported:
- Windows 7 or higher.
- MySQL 3.23 or higher.
- SQL Azure.

Step by Step Wizard:

Configure MySQL Data Source
- In the "Choose a Data Source" dialog:
  - Select "MySQL"
- Enter server details:
  - Server name: localhost (default)
  - Port: 3306 (default)
- Provide authentication:
  - Username: root (default)
  - Associated password
- Database selection:
  - Click the Refresh button to list available databases
  - Select target database from the list
Fig. 1: MySQL data source configuration
Configure SQL Azure Data Destination
- Prerequisite:
  - Enable access in Azure server's "Firewalls and virtual networks" page
  - Add your client IP to the firewall rules
- In the "Choose a Data Destination" dialog:
  - Select "SQL Azure"
- Enter server details:
  - Server name: e.g., esf.database.windows.net
  - Port: 1433 (default)
- Provide authentication credentials:
  - Username and password
- Database selection:
  - Click Refresh Database to load databases
  - Select target database
- Schema selection:
  - Click Refresh Schema to load schemas
  - Choose existing schema (dbo schema is default)
Fig. 2: SQL Azure data destination configuration
In "Select Source Table(s) & View(s)" Dialog
- Select migration objects: Choose tables or views to include in the migration.
  
  Fig. 3: Select tables and views
- Modify table structure: Click the ellipsis (...) button to access table options and schema adjustments.
  
  Fig. 4: Do transform
- Configure field mapping: In the Field Mapping options:
  - Customize destination fields (name, data type, default value, comments)
  - Select data transfer method:
    - Overwrite Table (replace existing data)
    - Empty Data (truncate before insert)
    - Append Data (add to existing data)
    - Skip Table (exclude from transfer)
  - Apply data filters before transfer
Execution Dialog
- Start migration: Click "Submit" to initiate automated data transfer from MySQL to SQL Azure.
  
  Fig. 5: Execute migration
- Monitor progress: Click "Browse Log" for real-time migration tracking, including issue resolution details.
- Save configuration: Click "Save as job" to store settings for:
  - Quick reloads of migration jobs
  - Command-line execution (use: dmtc.exe --help for parameter options)
Finished!

After migration completes, the toolkit generates a comprehensive report for verifying migration accuracy. You can monitor progress as the automated process runs efficiently. For any questions or feedback, contact us – our team is ready to assist.