SQL Server to MariaDB

BladePipe supports data replication from SQL Server to MariaDB. View supported migration, sync, verification, and connector capabilities.

Target DataSource：

MariaDB

Connection

Function	Description
Schema Migration	If the target schema does not exist, BladePipe will automatically generate and execute CREATE statements based on the source metadata and the mapping rule.
Full Data Migration	Migrate data by sequentially scanning data in tables and writing it in batches to the target database.
Incremental Data Sync	Sync of common DML like INSERT, UPDATE, DELETE is supported. UPDATE and DELETE for tables without primary keys are not synced by default (manual selection required).
Data Verification and Correction	Verify all existing data. Optionally, you can correct the inconsistent data based on verification results. Scheduled DataTasks are supported. For more information, see Create Verification and Correction DataJob.
Subscription Modification	Add, delete, or modify the subscribed tables with support for historical data migration. For more information, see Modify Subscription.
Table Name Mapping	Support the mapping rules, namely, keeping the name the same as that in Source, converting the text to lowercase, converting the text to uppercase, truncating the name by "_digit" suffix.
DDL Sync	Supports ALTER TABLE ADD COLUMN and DROP COLUMN.

Function	Description
Removal of Target Data before Full Data Migration	Remove the existing data in the Target before running the Full Data Migration, applicable for DataJobs reruning and scheduled Full Data migrations.
Recreating Target Table	Recreate target tables before running the Full Data Migration, applicable for DataJobs reruning and scheduled Full Data migrations.
Incremental Data Write Conflict Resolution Rule	IGNORE: Ignore primary key conflicts (skip writing), REPLACE: Replace the entire row in case of primary key conflicts.
Handling of Zero Value for Time	Allow setting zero value for time to different data types to prevent errors when writing to the Target.
Custom Code	For more information, see Custom Code Processing, Debug Custom Code and Logging in Custom Code.
Data Filtering Conditions	Support data filtering using WHERE conditions, with SQL-92 as the SQL language. For more information, see Data Filtering.
Adding Virtual Columns	Support adding custom virtual columns with fixed values, such as region, ID, etc.
Setting Target Primary Key	Change the primary key to another field to facilitate data aggregation and other operations.

Prerequisite	Description
Permissions for Account	See Required Permissions for SQL Server.
Enable SQL Server CDC	Run: exec [your_database].sys.sp_cdc_enable_db

Parameter	Description
maxTxsPerIteration	Maximum number of transactions to scan each time in incremental data sync.
scanParallel	Full data stage: The number of tables to be scanned in parallel. Incremental stage: The number of CDC tables to be scanned in parallel.
eventStoreSize	Size of the cache for parsed incremental events.

Tips: To modify the general parameters, see General Parameters and Functions.

Prerequisite	Description
Permissions for Account	See Permissions Required for MySQL/MariaDB.
Port Preparation	Allow the migration and sync node (Worker) to connect to the MySQL/MariaDB port (e.g., 3306).

Parameter	Description
keyConflictStrategy	Strategy for handling primary key conflicts during write in Incremental DataTask: IGNORE: Ignore conflicts (default) REPLACE: Replace conflicts (optional)
dstWholeReplace	Convert INSERT and UPDATE operations into full row replacement in the Target.
deCycle	Enable filtering in bidirectional sync to filter DML/DDL with specific markers.
specialSqlMode	Set a specific SQL mode when initializing the connection between databases.
defaultGisSRID	Set the SRID for GIS data types.
dstTimeZone	Target time zone, e.g., +08:00, Asia/Shanghai, America/New_York, etc.
increParallelApplyStrategy	Parallel write strategy for relational databases in the Target: KEY: Parallel writing to partitions separated based on primary keys. TABLE: Parallel writing to partitions separated based on tables. KEY_UPGRADE_TABLE: Parallel writing to partitions separated based on primary keys. Upgrade the partition to a table if there is an update to the unique key.

Tips: To modify the general parameters, see General Parameters and Functions.