All Products
Search

This Product

    AnalyticDB:Synchronize data using Federated Analytics

    Document Center

    AnalyticDB:Synchronize data using Federated Analytics

    Last Updated:Aug 20, 2026

    Federated Analytics uses the free, high-speed Data Pipeline Service (APS) of AnalyticDB for MySQL to synchronize data in real time from PolarDB for MySQL to an Enterprise Edition, Basic Edition, or Data Lakehouse Edition cluster, providing a one-stop solution for data synchronization and management.

    You can also join the Data Lakehouse Edition experience group (DingTalk group ID: 33600023146) to learn more about Federated Analytics.

    Important

    • The PolarDB for MySQL Federated Analytics feature was upgraded on July 23, 2024. The entry point for this feature has been removed, and you can no longer create new jobs. You can create synchronization jobs on the Data Integration page of the PolarDB console. For more information, see Synchronize data using zero-ETL.

    • If you have existing Federated Analytics jobs, you can continue to manage them through the Federated Analytics entry point in the China (Hangzhou), China (Shanghai), China (Shenzhen), China (Beijing), and US (Virginia) regions.

    Prerequisites

    • The PolarDB for MySQL instance and the AnalyticDB for MySQL Enterprise Edition, Basic Edition, or Data Lakehouse Edition cluster are in the same region. For more information, see Create an instance and Create a cluster.

    • The PolarDB for MySQL instance has binary logging enabled.

    Limitations

    • Federated Analytics for PolarDB for MySQL supports only AnalyticDB for MySQL clusters of Enterprise Edition, Basic Edition, and Data Lakehouse Edition.

    • Federated Analytics is available only in the following regions: China (Beijing), China (Hangzhou), China (Shanghai), China (Shenzhen), China (Hong Kong), Japan (Tokyo), Singapore, Malaysia (Kuala Lumpur), Indonesia (Jakarta), US (Silicon Valley), US (Virginia), Germany (Frankfurt), and UK (London).

    • You can create a maximum of 3 synchronization jobs for a single PolarDB for MySQL instance and a maximum of 30 synchronization jobs per region.

    Create a synchronization job

    1. Log on to the PolarDB console.

    2. In the upper-left corner of the page, select the region where the target instance is located.

    3. In the left-side navigation pane, click Federated Analytics .

    4. Click Create Job. In the Create Job panel, configure the following parameters:

      Parameter

      Description

      Job name

      Specify a custom name for the job. The default format is data-sync-<timestamp>.

      PolarDB for MySQL cluster

      The ID of the source PolarDB for MySQL instance.

      Source database account name

      Federated Analytics automatically creates a database account for the PolarDB for MySQL instance to perform data synchronization. The account name starts with sync. Do not delete or rename this account.

      AnalyticDB for MySQL instance

      The destination AnalyticDB for MySQL cluster.

      You can select an existing AnalyticDB for MySQL cluster or click Click to create an AnalyticDB for MySQL cluster to create a new AnalyticDB for MySQL cluster.

      Advanced Settings

      This option is disabled by default. When disabled, the job synchronizes the entire source instance.

      Enable this option to configure the Databases and Tables to Synchronize and Partition Key for Large Tables parameters.

      Databases and Tables to Synchronize

      Select the databases and tables to synchronize. By default, the job synchronizes all databases and tables from the source.

      Important

      • Tables without a primary key are not supported and are automatically excluded.

      • Each AnalyticDB for MySQL cluster can have a maximum of 2,048 databases. For more information, see Limitations.

      Partition Key for Large Tables

      To improve data write and query performance, we recommend that you set a partition key.

      The following partition formats are supported:

      • value: partitions data by value.

      • yyyyMMdd: partitions data by year, month, and day.

      • yyyyMM: partitions data by year and month.

      • yyyy: partitions data by year.

    5. Click OK. The job starts automatically.

      The Federated Analytics page displays the jobs you have created. You can also View, Edit, Delete, Suspend, or Start a synchronization job from the Actions column.

      Important

      You cannot recover deleted jobs.

    6. Click the destination instance ID to go to the AnalyticDB for MySQL console. You can perform data analysis in the AnalyticDB for MySQL console.