Help Center/ Data Replication Service/ Real-Time Synchronization/ To the Cloud/ From Microsoft SQL Server to GaussDB(for MySQL)
Updated on 2024-09-25 GMT+08:00

From Microsoft SQL Server to GaussDB(for MySQL)

Supported Source and Destination Databases

Table 1 Supported databases

Source DB

Destination DB

  • On-premises Microsoft SQL Server (Enterprise Edition 2012, 2014, 2016, 2017, 2019 and 2022 and Standard Edition 2016 SP2 or later, 2017, 2019 and 2022)
  • ECS-hosted Microsoft SQL Server (Enterprise Edition 2012, 2014, 2016, 2017, 2019 and 2022 and Standard Edition 2016 SP2 or later, 2017, 2019 and 2022)
  • Microsoft SQL Server-compatible databases on other clouds (Enterprise Edition 2012, 2014, 2016, 2017, 2019 and 2022 and Standard Edition 2016 SP2 or later, 2017, 2019 and 2022)
  • RDS for SQL Server (Enterprise Edition 2012, 2014, 2016, 2017, 2019 and 2022 and Standard Edition 2016 SP2 or later, 2017, 2019 and 2022)

GaussDB(for MySQL) Primary/Standby

Only whitelisted users can use this function.

Supported Synchronization Objects

Table 2 lists the objects that can be synchronized in different scenarios. DRS will automatically check the objects you selected before the synchronization.

Table 2 Supported synchronization objects

Type

Precautions

Synchronization objects

  • Supported field types:

    TINYINT, SMALLINT, INT, BIGINT, DECIMAL, NUMERIC, FLOAT, REAL, SMALLMONEY, MONEY, BIT, DATE, SMALLDATETIME, DATETIME, DATETIME2, DATETIMEOFFSET, TIME, TIMESTAMP, XML, CHAR, VARCHAR, NCHAR, NVARCHAR, BINARY, VARBINARY, IMAGE, NTEXT, TEXT, and UNIQUEIDENTIFIER

  • Unsupported field types: HIERARCHYID, TABLE, SQL_VARIANT, GEOMETRY, and GEOGRAPHY
  • Scope of full synchronization
    • Table structures, data, and indexes of selected tables can be synchronized.
    • The following functions can be used as default values during table structure synchronization: now, newid, getutcdate, and getdate. To use these functions as default values, ensure that the destination database has the same functions. If the destination database does not have the corresponding function, the following results may be displayed:

      1. The default value may be left empty.

      2. The table fails to be created. As a result, the object comparison result is inconsistent or the task fails.

    • A database or table name can contain a maximum of 64 characters, including only letters, digits, underscores (_), and hyphens (-).
    • The number of tables selected for the synchronization object cannot exceed 1000. If there are more than 1000 tables, you are advised to synchronize them in batches. (Create a new task after the synchronization task is complete.)
    • Transparent Data Encryption (TDE) encrypted databases in the source instance cannot be synchronized. If you do not need to synchronize TDE encrypted databases, deselect them. If you need to synchronize TDE encrypted databases, disable TDE first.
    • Column encryption is not supported.
    • Auto-increment columns cannot be synchronized.
    • Computed columns in the source database cannot be written to computed columns in the destination database. They can be written to common columns in the destination database.
  • Scope of incremental synchronization
    • DML statements, including INSERT, UPDATE, and DELETE, are supported.
    • DDL statements are not supported.

Database Account Permission Requirements

To start a synchronization task, the source and destination database users must meet the requirements in the following table. Different types of synchronization tasks require different permissions. For details, see Table 3. DRS automatically checks the database account permissions in the pre-check phase and provides handling suggestions.

Table 3 Database account permission

Type

Full+Incremental Synchronization

Source database user

At least the sysadmin or view server state and db_datareader or db_owner permissions for databases to be synchronized

Destination database user

The user must have the SELECT, CREATE, DROP, INSERT, DELETE, UPDATE, ALTER, REFERENCES and INDEX permissions.

Precautions

The full+incremental synchronization consists of four phases: task startup, full synchronization, incremental synchronization, and task completion. To ensure smooth synchronization, read the following notes before creating a synchronization task.

Table 4 Precautions

Type

Constraints

Starting a task

  • Source database parameter requirements:
    • The source database mode must be set to FULL.
    • SQL Server Agent must be enabled for the source database.
    • If Force Protocol Encryption is set to Yes for the source database, Trust Server Certificate also must be set to Yes, as shown in Figure 1.
      Figure 1 Client configuration
  • Source database object requirements:
    • If the source database contains disabled clustered indexes of tables, the synchronization fails.
    • Names of the databases, schemas, and tables to be synchronized in the source database can contain a maximum of 64 characters, including only letters, digits, underscores (_), and hyphens (-).
    • Names of the columns in the source table cannot contain the following special characters: []?.,
    • The SQL Server character type uses the number of bytes as the length, and the GaussDB(for MySQL) character type uses the number of characters as the length and the character set is utf8mb4. Therefore, the number of bytes occupied by a field in the destination database is n x 4.
    • The length of each index cannot exceed 3,072 bytes after being converted into a field in the destination database.
    • The total number of indexes cannot exceed 64.
    • The total length of fields after being mapping to the destination database cannot exceed 66,535 bytes.
  • Destination database object requirements:
    • The destination database must be a primary/standby GaussDB(for MySQL) instance.
    • The destination DB instance must have sufficient storage space.
    • The destination DB instance cannot contain databases with the same name as the source database (except system databases).
  • Other notes:
    • Do not perform primary/standby switchover on the source database. Otherwise, the synchronization task will fail.
    • The source Microsoft SQL Server database using TLS 1.0 or TLS 1.1 cannot be synchronized. If data synchronization is required, you are advised to upgrade TLS version of the source database to TLS 1.2 or later.
    • Incremental synchronization of the source SQL Server database is based on the CDC capability provided by the SQL Server database. If CDC of the source SQL Server database is abnormal (for example, CDC is disabled or the transaction log is full), incremental synchronization will be affected.
    • Do not use an imprecise value, such as floating-point type and date type, as a primary key or an equivalent condition after WHERE in the database. This feature affects the synchronization of UPDATE and DELETE statements in the DRS incremental scenario and causes value comparison to be unavailable. For details about the data type mapping, see Mapping Data Types from Microsoft SQL Server to GaussDB(for MySQL).
    • Object names will be converted to lowercase letters after being synchronized to the destination database. Therefore, the selected source database tables cannot contain tables with the same name but different letter cases. Otherwise, the synchronization fails.
    • Some SQL Server databases (such as Azure SQL) do not support the use syntax and do not support synchronization of multiple databases. If you need to synchronize multiple databases, create multiple synchronization tasks.

Full synchronization

  • Do not change the port of the source and destination databases, or change or delete the passwords and permissions of the source and destination database users. Otherwise, the task may fail.
  • Do not run any DDL statement in the source database. Otherwise, data may be inconsistent or the task may fail.
  • Do not write data to the destination database. Otherwise, data may be inconsistent.
  • To ensure normal synchronization and data consistency, you are advised to create a DRS task again during off-peak hours to meet the preceding requirements.

Incremental synchronization

  • Do not change the port of the source and destination databases, or change or delete the passwords and permissions of the source and destination database users. Otherwise, the task may fail.
  • Do not write data to the destination database. Otherwise, data may be inconsistent.
  • To ensure normal synchronization and data consistency, you are advised to create a DRS task again during off-peak hours to meet the preceding requirements.
  • DDL operations performed on the source database will not be synchronized to the destination database.
  • The IMAGE, TEXT, and NTEXT big data types cannot be deleted.

Synchronization comparison

  • You are advised to compare data during off-peak hours of the source database to prevent inconsistent data from being falsely reported and reduce the impact on the source database and DRS tasks.
  • During incremental synchronization, if data is written to the source database, the comparison results may be inconsistent.
  • Data cannot be compared during full synchronization.
  • Do not limit the synchronization speed during data comparison.

Procedure

  1. On the Data Synchronization Management page, click Create Synchronization Task.
  2. On the Create Synchronization Instance page, select a region and project, specify the task name, description, and the synchronization instance details, and click Create Now.

    • Task information description
      Figure 2 Synchronization task information
      Table 5 Task information

      Parameter

      Description

      Region

      The region where the replication instance is deployed. You can change the region.

      Project

      The project corresponds to the current region and can be changed.

      Task Name

      The task name must start with a letter and consist of 4 to 50 characters. It can contain only letters, digits, hyphens (-), and underscores (_).

      Description

      The description consists of a maximum of 256 characters and cannot contain special characters !=<>'&"\

    • Synchronization instance details
      Figure 3 Synchronization instance details
      Table 6 Synchronization instance information

      Parameter

      Description

      Data Flow

      Select To the cloud.

      Source DB Engine

      Select Microsoft SQL Server.

      Destination DB Engine

      Select GaussDB(for MySQL).

      Network Type

      Available options: VPC, Public network and VPN or Direct Connect. Public network is used as an example.

      • VPC is suitable for data synchronization between cloud databases of the same account in the same region and VPC.
      • Public network is suitable for data synchronization from on-premises or external cloud databases to the destination databases bound with an EIP.
      • VPN or Direct Connect is suitable for data synchronization from on-premises databases to cloud databases, between databases of different accounts in the same region on the cloud, or between databases across regions on the cloud using a VPN, Direct Connect, Cloud Connect, VPCEP, or a VPC peering connection.

      DRS Task Type

      Type of the DRS task. The value can be Single-AZ or Dual-AZ.

      • Dual-AZ: This architecture provides HA, improving the reliability of DRS tasks. After a dual-AZ task is created, DRS creates two subtasks, each running in the primary and standby AZs. If the subtask in the primary AZ fails, DRS automatically starts the subtask in the standby AZ to continue the synchronization. This deployment is for scenarios where there is a lot of service data, long-term synchronization is required, and there are strict limits on how much service downtime can be tolerated.
      • Single-AZ: Single-node deployment is used. The synchronization task will be created on only one node to save money. This deployment is for scenarios where there is a small amount of service data, short-term synchronization is required, and there is no requirement on service downtime.

      This option is available only in specific scenarios. For details, see Performing a Switchover for a Dual-AZ Task.

      Destination DB Instance

      Select a GaussDB(for MySQL) instance you created.

      Synchronization Instance Subnet

      Select the subnet where the synchronization instance is located. You can also click View Subnets to go to the network console to view the subnet where the instance resides.

      By default, the DRS instance and the destination DB instance are in the same subnet. You need to select the subnet where the DRS instance resides, and there are available IP addresses for the subnet. To ensure that the synchronization instance is successfully created, only subnets with DHCP enabled are displayed.

      Synchronization Mode

      The synchronization mode supported by a DRS task. Full+Incremental is used as an example. For details about the underlying working principles for full or incremental synchronization, see Product Architecture and Function Principles.

      • Full+Incremental

        This synchronization mode allows you to synchronize data in real time. After a full synchronization initializes the destination database, an incremental synchronization parses logs to ensure data consistency between the source and destination databases.

      • Full

        All objects and data in non-system databases are synchronized to the destination database at a time. This mode is applicable to scenarios where service interruption is acceptable.

      • Incremental

        Through log parsing, incremental data generated on the source database is synchronized to the destination database.

      Specify EIP

      This parameter is available when you select Public network for Network Type. Select an EIP to be bound to the DRS instance. DRS will automatically bind the specified EIP to the DRS instance and unbind the EIP after the task is complete. The number of specified EIPs must be the consistent with that of DB instances.

      If DRS Task Type is set to Dual-AZ, you need to specify the primary and standby IP addresses.

      For details about the data transfer fee generated using a public network, see EIP Price Calculator.

    • AZ
      Figure 4 AZ
      Table 7 Task AZ

      Parameter

      Description

      AZ

      Select the AZ where you want to create the DRS task. Selecting the one housing the source or destination database can provide better performance.

      If DRS Task Type is set to Dual-AZ, you can specify Primary AZ and Standby AZ.

      Figure 5 AZ
    • Enterprise Project and Tags
      Figure 6 Enterprise projects and tags
      Table 8 Enterprise Project and Tags

      Parameter

      Description

      Enterprise Project

      An enterprise project you would like to use to centrally manage your cloud resources and members. Select an enterprise project from the drop-down list. The default project is default.

      For more information about enterprise project, see Enterprise Management User Guide.

      To customize an enterprise project, click Enterprise in the upper right corner of the console. The Enterprise Project Management Service page is displayed. For details, see Creating an Enterprise Project in Enterprise Management User Guide.

      Tags

      • Tags a task. This configuration is optional. Adding tags helps you better identify and manage your tasks. Each task can have up to 20 tags.
      • If your organization has configured tag policies for DRS, add tags to tasks based on the policies. If a tag does not comply with the policies, task creation may fail. Contact your organization administrator to learn more about tag policies.
      • After a task is created, you can view its tag details on the Tags tab. For details, see Tag Management.

    If a task fails to be created, DRS retains the task for three days by default. After three days, the task automatically stops.

  3. On the Configure Source and Destination Databases page, wait until the synchronization instance is created. Then, specify source and destination database information and click Test Connection for both the source and destination databases to check whether they have been connected to the synchronization instance. After the connection tests are successful, select the check box before the agreement and click Next.

    Establish the connectivity between the DRS instance and the source and destination databases.

    • Network connectivity: Ensure that the source and destination databases accept connections from the DRS instance. To access databases over a public network, configure the database to accept connections from the EIP of the DRS instance. To access databases over a VPC, VPN, or Direct Connect network, configure the database to accept connections from the private IP address of the DRS instance. For details, see Network Preparations.
    • Account connectivity: Ensure that the source and destination databases allows connections from the DRS instance using the username and password.
    • Source database information
      Figure 7 Source database information
      Table 9 Source database settings

      Parameter

      Description

      Database Type

      Select RDS DB instance.

      DB Instance Name

      Select the Microsoft SQL Server DB instance to be synchronized as the source DB instance.

      Database Username

      The username for logging in to the source Microsoft SQL Server database.

      Database Password

      The password for the database username.

      • Destination database information
        Figure 8 Destination database information
        Table 10 Destination database settings

        Parameter

        Description

        DB Instance Name

        The GaussDB(for MySQL) instance selected during synchronization task creation. This parameter cannot be changed.

        Database Username

        The username for accessing the destination database.

        Database Password

        The password for the database username. You can change the password if necessary.

        SSL Connection

        If SSL connection is required, enable SSL on the destination database, ensure that related parameters have been correctly configured, and upload an SSL certificate.

        NOTE:
        • The maximum size of a single certificate file that can be uploaded is 500 KB.
        • If SSL is disabled, your data may be at risk.

    The username and password of the source and destination databases are encrypted and stored in the databases and the synchronization instance during the synchronization. After the task is deleted, the username and password are permanently deleted.

  4. On the Set Synchronization Task page, select the synchronization object type and synchronization objects, and click Next.

    Figure 9 Synchronization Mode
    Table 11 Synchronization Object

    Parameter

    Description

    Flow Control

    You can choose whether to control the flow. Flow Control takes effect in the full phase only.

    • Yes

      You can customize the maximum synchronization speed. During the full synchronization, the synchronization speed of each task (or each subtask in multi-task mode) does not exceed the value of this parameter.

      In addition, you can set the time range based on your service requirements. The traffic rate setting usually includes setting of a rate limiting time period and a traffic rate value. Flow can be controlled all day or during specific time ranges. The default value is Always. A maximum of three time ranges can be set, and they cannot overlap.

      The flow rate must be set based on the service scenario and cannot exceed 9,999 MB/s.

      Figure 10 Flow control
    • No
      The synchronization speed is not limited and the outbound bandwidth of the source database is maximally used, which will increase the read burden on the source database. For example, if the outbound bandwidth of the source database is 100 MB/s and 80% bandwidth is used, the I/O consumption on the source database is 80 MB/s.
      NOTE:
      • The flow control mode takes effect only in the full synchronization phase.
      • You can also change the flow control mode after creating a task. For details, see Modifying the Flow Control Mode.

    Synchronization Object Type

    You can select Table structure, Data, or Index for Synchronization Object Type for full synchronization.

    • Data is selected by default.
    • If Table structure is selected, the destination database cannot contain tables whose names are the same as the source tables to be synchronized.
    • If Table structure is not selected, the destination database must have tables that match the source tables, and the table structure must be the same as the selected source table structures.

    Incremental Conflict Policy

    The conflict policy refers to the conflict handling policy during incremental synchronization. By default, conflicts in the full synchronization phase are ignored. Select any of the following conflict policies:

    • Ignore

      The system will skip the conflicting data and continue the subsequent synchronization process. If you select Ignore, data in the source database may be inconsistent with that in the destination database.

    • Overwrite

      Conflicting data will be overwritten.

    Synchronize DML

    Select the DML operations to be synchronized. By default, all DML operations are selected.

    If you do not select Delete, DELETE statements in the incremental data of the source database will not be synchronized, which may cause a data inconsistency. As a result, there may be a data conflict or the task may fail.

    Synchronization Object

    The left pane displays the source database objects, and the right pane displays the selected objects. You can select Tables or Import object file for Synchronization Object as required.

    • If the synchronization objects in source and destination databases have different names, you can map the source object name to the destination one. For details, see Changing Object Names (Mapping Object Names).
    • The number of tables selected for the synchronization object cannot exceed 1000. If there are more than 1000 tables, you are advised to synchronize them in batches. (Create a new task after the synchronization task is complete.)
    • For details about how to import an object file, see Importing Synchronization Objects.
    NOTE:
    • To quickly select the desired database objects, you can use the search function.
    • If there are changes made to the source databases or objects, click in the upper right corner to update the objects to be synchronized.
    • If an object name contains spaces, the spaces before and after the object name are not displayed. If there are two or more consecutive spaces in the middle of the object name, only one space is displayed.
    • The name of the selected synchronization object cannot contain spaces.

  5. On the Check Task page, check the synchronization task.

    • If any check fails, review the cause and rectify the fault. After the fault is rectified, click Check Again.

      For details about how to handle check failures, see Solutions to Failed Check Items in Data Replication Service User Guide.

    • If all check items are successful, click Next.

      You can proceed to the next step only when all checks are successful. If there are any items that require confirmation, view and confirm the details first before proceeding to the next step.

  6. On the displayed page, specify Start Time, Send Notifications, SMN Topic, Delay Threshold (s), and Stop Abnormal Tasks After, confirm that the configured information is correct, select the check box before the agreement, and click Submit to submit the task.

    Figure 11 Task startup settings

    Table 12 Task startup settings

    Parameter

    Description

    Start Time

    Set Start Time to Start upon task creation or Start at a specified time based on site requirements.

    NOTE:

    After a synchronization task is started, the performance of the source and destination databases may be affected. You are advised to start a synchronization task during off-peak hours.

    Send Notifications

    This parameter is optional. After enabled, select a SMN topic. If the status, latency metric, or data of the migration task is abnormal, DRS will send you a notification.

    SMN Topic

    This parameter is available only after you enable Send Notifications and create a topic on the SMN console and add a subscriber.

    For details, see Simple Message Notification User Guide.

    Delay Threshold (s)

    During an incremental synchronization, a synchronization delay indicates a time difference (in seconds) of synchronization between the source and destination database.

    If the synchronization delay exceeds the threshold you specify, DRS will send alarms to the specified recipients. The value ranges from 0 to 3,600. To avoid repeated alarms caused by the fluctuation of delay, an alarm is sent only after the delay has exceeded the threshold for six minutes.

    NOTE:
    • If the delay threshold is set to 0, no notifications will be sent to the recipient.
    • In the early stages of an incremental synchronization, the synchronization delay is long because a large quantity of data is awaiting synchronization. In this case, no notifications will be sent.
    • Before setting the delay threshold, enable Send Notifications.

    Data Exception Notification

    This parameter is optional. After enabled, DRS will send a notification if the task data is abnormal.

    Stop Abnormal Tasks After

    Number of days after which an abnormal task is automatically stopped. The value must range from 14 to 100. The default value is 14.

    NOTE:
    • You can set this parameter only for pay-per-use tasks.
    • Tasks in the abnormal state are still charged. If tasks remain in the abnormal state for a long time, they cannot be resumed. Abnormal tasks run longer than the period you set (unit: day) will automatically stop to avoid unnecessary fees.

  7. After the task is submitted, you can view and manage it on the Data Synchronization Management page.

    • You can view the task status. For more information about task status, see Task Statuses.
    • You can click in the upper right corner to view the latest task status.
    • By default, DRS retains a task in the Configuration state for three days. After three days, DRS automatically deletes background resources, but the task status remains unchanged. When you configure the task again, DRS applies for resources for the task again. In this case, the IP address of the DRS instance changes.
    • For a public network task, DRS needs to delete background resources after you stop the task. The EIP bound to the task cannot be restored to the Unbound state until background resources are deleted.