Batch sync nodes support various types of data stores, including MaxCompute, MySQL, Distributed Relational Database Service (DRDS), SQL Server, PostgreSQL, Oracle, MongoDB, Db2, Tablestore, Object Storage Service (OSS), FTP, HBase, LogHub, Hadoop Distributed File System (HDFS), and Stream. This topic describes how to create a batch sync node.

Background information

When you enter a table name, an object list appears, which displays all matched tables. Only exact match is supported. Therefore, you must enter a complete table name. Tables are labeled as unsupported if they are not supported by batch sync nodes.

If you move the pointer over a table in the list, the details of the table are displayed, including the database, IP address, and owner of the table. The details help you select the correct table. After you select and click a table, the column information is automatically entered. You can add, move, or delete columns.


  1. Go to the DataStudio page.
    1. Log on to the DataWorks console.
    2. In the left-side navigation pane, click Workspaces.
    3. In the top navigation bar, select the region in which the workspace that you want to manage resides. Find the workspace and click DataStudio in the Actions column.
  2. Move the pointer over the Create icon and choose Data Integration > Batch Synchronization.
    Alternatively, you can find the required workflow, right-click Data Integration, and then choose Create > Batch Synchronization.
  3. In the Create Node dialog box, configure the Name and Path parameters.
  4. Click Commit.
  5. Configure the batch sync node. For more information, see Configure a batch synchronization node by using the codeless UI.
  6. Commit the node.
    Important You must set the Rerun and Parent Nodes parameters before you can commit the node.
    1. Click the Commit icon in the toolbar.
    2. In the Commit Node dialog box, enter your comments in the Change description field.
    3. Click OK.
    In a workspace in standard mode, you must click Deploy in the upper-right corner after you commit the do-while node.
  7. Test the node. For more information, see View and manage auto triggered nodes.