Create an SQL file parsing task

In performance assessment, an SQL file parsing task organizes the selected source traffic into a format specific to migration assessment for playback. This topic describes how to create an SQL file parsing task.

Prerequisites

Before creating an SQL file parsing task, you must obtain the audit logs from the corresponding source database.

• If you select Source Database Type as Aurora MySQL, AWS_MYSQL, RDS_MYSQL, POLAR_MYSQL, or GCP_MYSQL, for details, see Obtain traffic files for a database instance.

• If you select Source Database Type as HUAWEI_RDS_MySQL, for details, see Enable SQL audit logging.

• If you select Source Database Type as HUAWEI_DWS, for details, see Dump database audit logs.

Limitations

• Only users with the project roles of Project Administrator or Data Services Administrator can create an SQL file parsing task.

• Performance assessment only supports parsing files from the source database.

Procedure

1. Create an SQL file parsing and assessment task.

   

   1. Log in to the OceanBase Cloud console.

   2. In the left-side navigation pane, click Data Services > Data Migration.

   3. On the Data Migration page, click the Assess Performance tab.

   4. On the Assess Performance tab, click Create in the upper-right corner > SQL File Parsing.

2. On the Set Up Source Database page, configure the parameters.

   Parameter	Description
   Task Name	The name of the assessment task, which must not exceed 30 characters.
   Instance Source	Currently supports AWS, HUAWEI, ALIYUN, and Google Cloud.
   Source Database Type	If Cloud Vendor is set to AWS, the source database types are Aurora MySQL and AWS_MYSQL. If Cloud Vendor is set to HUAWEI, the source database types are HUAWEI_RDS_MySQL and HUAWEI_DWS. If Cloud Vendor is set to ALIYUN, the source database types are RDS_MYSQL and POLAR_MYSQL. If Cloud Vendor is set to Google Cloud, the source database type is GCP_MYSQL.
   Region	Select the region where the source database is located.
   Source Database Instance	When Source Database Type is set to Aurora MySQL, AWS_MYSQL, HUAWEI_DWS, RDS_MYSQL, POLAR_MYSQL, or GCP_MySQL, you need to enter the source database instance. For details about how to view the database instance name, see Query a database instance. Separate multiple database instances with commas (,).
   Source Database	This parameter is displayed only when Cloud Vendor is set to Google Cloud.

3. Click Next. On the Configure Data Collection page, configure the parameters.

   • If the instance source is Google Cloud, Data Collected From supports only Import Object Storage (Google Cloud Object Storage).

     If the instance source is AWS, Data Collected From supports S3 Import and Upload File.

     If the instance source is ALIYUN, Data Collected From supports Import Object Storage Service (OSS) and Upload File.

     If you have saved the audit logs of an Aurora MySQL or AWS MySQL instance to S3, or the audit logs of an Alibaba Cloud RDS_MySQL or Polar_MySQL instance to OSS, select S3 Import or Import Object Storage Service (OSS) to import the audit logs for assessment. For details about how to obtain the traffic files of GCP MySQL, Aurora MySQL, AWS_MySQL, RDS_MySQL, and Polar_MySQL instances, see Query the traffic files of a database instance.

     Note

     We strongly recommend that you create a dedicated user for the migration assessment service and grant permissions only for the relevant bucket. For information about the Alibaba Cloud account system, see Access control.

     Parameter	Description
     AccessKey Account	The AccessKey ID of the S3, GCS, or Alibaba Cloud account. For details about the AccessKey for S3 or GCS, see Create an AccessKey. For details about the AccessKey for Alibaba Cloud, see Create an AccessKey.
     AccessKey Secret	The AccessKey secret of the S3, GCS, or Alibaba Cloud account.
     S3/OSS Bucket for Log Import	Enter the name of the S3 or OSS bucket for log import.
     GCP Bucket for File Import	Enter the name of the GCP bucket for log import. This field is displayed only when the instance source is set to Google Cloud.
     File Delivery Directory	Enter the directory for delivering audit logs.
     Traffic Collection Time Range	Select the time range to be evaluated. The maximum selectable time range is 24 hours. If the obtained data is empty, it means no log files were generated within the selected time range.

     After configuring the parameters above, click Verify. If verification passes, Valid File List displays the files that can be parsed.

   • If you have saved the audit logs of an Aurora MySQL instance or AWS MySQL instance, or the traffic files from the Log Service (SLS), locally, or if the instance source is HUAWEI or ALIYUN, select Upload File to manually import a ZIP or GZ file for assessment. Note that the maximum supported upload size is 5 GB, and only one file can be uploaded.

4. Click Next. The system automatically performs a precheck.

5. After the precheck passes, click Start Now to begin executing the SQL file parsing task.

   After starting the task, you can view the assessment report on the Task List page. For more information, see View a performance assessment report. Files that have been parsed separately are saved on the Assess Performance > Parse files page.