Migrating data from SQL Azure to MariaDB

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

SQL Azure vs. MariaDB:

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.
MariaDB is a powerful open-source relational database management system (RDBMS) that originated as a fork of MySQL. It was developed by the original creators of MySQL in response to concerns over its acquisition by Oracle Corporation. MariaDB retains compatibility with MySQL while offering additional features, improved performance, and enhanced security. It is widely used in various applications ranging from small-scale web databases to large-scale enterprise systems, thanks to its flexibility, scalability, and active community support.

Prerequisite:

Software Required:

DMToolkit_x64.zip (63.6 MiB)	64-bit Windows application for ESF Database Migration Toolkit 12.2.08 (2025-07-11). (md5: e93a0ef57622bfd8ee77d6aa6e38c13b)
DMToolkit_win32.zip (58.8 MiB)	32-bit Windows application for ESF Database Migration Toolkit 12.2.08 (2025-07-11). (md5: bd34cb7f73c88c6d0c7a44069ad756d6)

System Supported:
- Windows 7 or higher.
- SQL Azure.
- MariaDB 5.1 or higher.

Step by Step Wizard:

Configure SQL Azure Connection
- Prerequisite:
  - Enable "Allow access to Azure services" in Azure SQL server settings
  - Add your client IP under Firewalls and virtual networks
- In the "Choose a Data Source" dialog:
  - Select "SQL Azure"
- Enter connection details:
  - Server name: e.g., esf.database.windows.net
  - Port: 1433 (default)
  - Authentication: Enter credentials
- Load database options:
  - Click the Refresh Database button
  - Select target database from list
- Load schema options:
  - Click the Refresh Schema button
  - Choose desired schema
Fig. 1: SQL Azure data source configuration
Configure MariaDB Destination
- In the "Choose a Destination" dialog:
  - Select "MariaDB"
- Enter connection details:
  - Server name: localhost (default)
  - Port: 3306 (default)
  - Username
  - Password
- Optional settings:
  - Select MariaDB Storage Engine
  - Choose character set (e.g., UTF-8)
- Database configuration:
  - Click the Refresh button to list available databases
  - Select existing database OR enter new database name
  - Note: Non-existent databases will be automatically created during migration
Fig. 2: MariaDB 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 SQL Azure to MariaDB.
  
  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.