diff --git a/product/en/docs-sca/v5.1/overview.md b/product/en/docs-sca/v5.1/overview.md index 9b947151c2daa0175a59a892516cada134993322..9c0c4c146fe46f484d4e5310e20cb5b0035d84e8 100644 --- a/product/en/docs-sca/v5.1/overview.md +++ b/product/en/docs-sca/v5.1/overview.md @@ -15,32 +15,32 @@ SCA currently supports three source databases, including: Oracle, MySQL, DB2, Po **Applicable to**: MogDB and other openGauss-based databases -SCA service program can run the following 14 types of tasks: +The SCA program can run the following 14 types of tasks: -* Runtime tasks +* Tasks related to program operation: - 1. `I [Initialize]`: **Initialize**, used to initialize the SCA repository - 2. `L [Apply License]`: **Apply license**, task for license application + 1. `I [Initialize]`: **Initialization**, used for initializing the SCA database. + 2. `L [Apply License]`: **License application**, used for tasks related to license applications. -* Collection tasks +* Tasks related to collection: - 1. `OC [Oracle Collection]`: **Oracle collection**, used to collect the business SQL executed in Oracle database, need long time to collect - 2. `MC [MySQL Collection]`: **MySQL collection**, used to collect the business SQL executed in MySQL database, need to configure the slow log in advance, and then collect at once - 3. `DC [DB2 Collection]`: **DB2 collection**, used to collect the business SQL executed in DB2 database, need long time to collect - 4. `PC [PostgreSQL Collection]`: **PostgreSQL collection**, used to collect the business SQL executed in PostgreSQL database (using plugin pg_stat_statements), need long time to collect - 5. `IC [Informix Collection]`: **Informix collection**, used to collect the business SQL executed in Informix database (need enable global sql tracing manually), need long time to collect - 6. `SC [SQL Server Collection]`: **SQL Server collection**, used to collect the business SQL executed in SQL Server database, need long time to collect + 1. `OC [Oracle Collection]`: **Oracle collection**, used for collecting business SQLs executed in Oracle databases, requires long-term collection. + 2. `MC [MySQL Collection]`: **MySQL collection**, used for collecting business SQLs executed in MySQL databases, requires pre-configuration of slow logs, then collected all at once. + 3. `DC [DB2 Collection]`: **DB2 collection**, used for collecting business SQLs executed in DB2 databases, requires long-term collection. + 4. `PC [PostgreSQL Collection]`: **PostgreSQL collection**, used for collecting business SQLs executed in PostgreSQL databases (dependent on the pg_stat_statements plugin), requires long-term collection. + 5. `IC [Informix Collection]`: **Informix collection**, used for collecting business SQLs executed in Informix databases (manual activation of global sql trace function required), requires long-term collection. + 6. `SC [SQL Server Collection]`: **SQL Server collection**, used for collecting business SQLs executed in SQL Server databases, requires long-term collection. -* Analysis tasks +* Tasks related to analysis: - 1. `OI [Oracle Inspection]`: **Oracle compatibility evaluation**, used to evaluate the actual compatibility of business SQL collected in Oracle on the source side in MogDB on the target side - 2. `MI [MySQL Inspection]`: **MySQL compatibility evaluation**, used to evaluate the actual compatibility of business SQL collected in MySQL on the source side in MogDB on the target side - 3. `DI [DB2 Inspection]`: **DB2 compatibility evaluation**, used to evaluate the actual compatibility of business SQL collected in DB2 on the source side in MogDB on the target side - 4. `PI [PostgreSQL Inspection]`: **PostgreSQL compatibility evaluation**, used to evaluate the actual compatibility of business SQL collected in PostgreSQL on the source side in MogDB on the target side - 5. `II [Informix Inspection]`: **Informix compatibility evaluation**, used to evaluate the actual compatibility of business SQL collected in Informix on the source side in MogDB on the target side - 6. `SI [SQL Server Inspection]`: **SQL Server compatibility evaluation**, used to evaluate the actual compatibility of business SQL collected in SQL Server on the source side in MogDB on the target side - 7. `OS [Oracle Simulation]`: **Oracle performance evaluation**, used to evaluate the execution performance of business SQL collected in Oracle on the source side in MogDB on the target side - 8. `OIS [Oracle Inspection & Simulation]`: **Oracle compatibility and performance evaluation**, equivalent to OI + OS two tasks at the same time + 1. `OI [Oracle Inspection]`: **Oracle compatibility assessment**, used to assess the actual compatibility of business SQLs collected from the source Oracle in the target MogDB. + 2. `MI [MySQL Inspection]`: **MySQL compatibility assessment**, used to assess the actual compatibility of business SQLs collected from the source MySQL in the target MogDB. + 3. `DI [DB2 Inspection]`: **DB2 compatibility assessment**, used to assess the actual compatibility of business SQLs collected from the source DB2 in the target MogDB. + 4. `PI [PostgreSQL Inspection]`: **PostgreSQL compatibility assessment**, used to assess the actual compatibility of business SQLs collected from the source PostgreSQL in the target MogDB. + 5. `II [Informix Inspection]`: **Informix compatibility assessment**, used to assess the actual compatibility of business SQLs collected from the source Informix in the target MogDB. + 6. `SI [SQL Server Inspection]`: **SQL Server compatibility assessment**, used to assess the actual compatibility of business SQLs collected from the source SQL Server in the target MogDB. + 7. `OS [Oracle Simulation]`: **Oracle performance assessment**, used to assess the execution performance of business SQLs collected from the source Oracle in the target MogDB. + 8. `OIS [Oracle Inspection & Simulation]`: **Oracle compatibility and performance assessment**, equivalent to conducting both OI + OS tasks simultaneously. Note: