Viewing Evaluation Project Details

Scenarios

This section describes how to view the detailed information of an evaluated project, including the source database analysis, database schema, and target database analysis. This helps you select the target database.

Prerequisites

Evaluated projects have been created.

Constraints

If Skip Target DB Evaluation is set to Yes (default value) when you create an evaluation project, there are only the basic information of recommended target databases on the Target DB Analysis tab.

Procedure

1. Log in to the UGO console.
2. In the navigation pane on the left, choose Schema Migration > DB Evaluation.

   All the evaluation projects are displayed in the list. You can view the project basic information, including the project name/ID, connection type, and project status. The project ID can be directly copied.

   If there are many projects, you can search for them by project status, tag, and project name/ID.

   Figure 1 Database evaluation
   

3. Click the name of the project that you want to view. The Source DB Analysis, Target DB Analysis, and Tags tabs are displayed.
   Figure 2 Evaluation information classification
   

   Table 1 Function description of the Source DB Analysis tab

   Function	Description
   Basic Information	Displays basic information, including the project name, source database type, database version, database name, number of instances, and database memory.
   Object Statistics	Displays the number of database objects. The objects displayed vary depending on the source database type. Click View Object Details to view details about the database schemas. For details, see Table 2. NOTE: The numbers of object types such as Cluster are not displayed.
   Object Distribution	Displays the database object statistics in a bar chart. Hovering over on a bar shows the exact values.

   

   Source DB analysis provides a reference for you to select a target database.

   Table 2 Function description of the DB Schema tab

   Function	Description
   Schema list	Displays the schema, object name, object type, and operation. If there is a large amount of data, you can search for your desire data by DDL collection status, schema, wrapped object status (only available for Oracle database), or object name. Incremental evaluation: The SQL data has to be incrementally evaluated if: The DDL collection status is Not collected. The wrapped objects are edited. Click View Details in the Operation column to view the detailed information and SQL script of the object. Locate an object and click Edit SQL in the Operation column to edit the SQL script of the object. NOTE: Edit SQL is available only when the target database is not confirmed and any of the following conditions is met: The wrapped objects are edited. The DDL Collection Status of objects is Collected. If Object Type is SQL for a schema, View Details is unavailable. When the source database type is DB2, incremental evaluation and SQL editing are not supported.
   DB Objects (for Oracle database)	Include storage objects, code objects, job objects, and management. You can click an object to view the corresponding information. Storage Objects: include SEQUENCE, TABLE, INDEX, SYNONYM, and TYPE. Code Objects: include VIEW, MATERIALIZED_VIEW, TRIGGER, TYPE_BODY, PROCEDURE, FUNCTION, PACKAGE, PACKAGE_BODY, and DIRECTORY. Job Objects: include CREDENTIAL, PROGRAM, SCHEDULE, JOB_CLASS, and JOB. Management: include USER, ROLE, and GRANT.
   DB Objects (for MySQL database)	Include storage objects, code objects, and management objects. You can click an object to view the corresponding information. Storage Objects: include TABLE, VIEW, and SYNONYM. Code Objects: include FUNCTION, PROCEDURE, and TRIGGER. Management Objects: includes GRANT, ROLE, and USER.
   DB Objects (for DB2 database)	Include storage objects and code objects. You can click an object to view the corresponding information. Storage Objects: include SCHEMA, SEQUENCE, TABLE, INDEX, SYNONYM, and TYPE. Code Objects: include VIEW, VARIABLE, TRIGGER, PROCEDURE, and FUNCTION.

   Table 3 Function description of the Target DB Analysis tab

   Function	Sub-function	Description
   Target database selection NOTE: The price is an estimate and may differ from the final price.	Summary Report	Click Summary Report to download the compatibility evaluation summary report in PDF format to the local PC. You can view basic information about the source database and analysis results of the target database in the report. If the source database type is DB2, this function is unavailable.
   	Database List	The information includes names, versions, and success rates of the target databases that you can select. NOTE: By default, the database with the highest success rate is selected. You can also select a database. The database compatibility evaluation changes as you change the target database. Comprehensive evaluation facilitates you to make a choice.
   	Confirm DB Selection	You can determine the target database type to complete the evaluation. If the target database has been confirmed, the button is unavailable.
   	Re-evaluate	This function is displayed only when Evaluation Status is Evaluation-success. Confirm Target DB Pending and Project Status is In progress. You can re-evaluate objects as needed. The time required depends on the number of objects. NOTE: If a project whose Evaluation Status is Evaluation-success. Confirm Target DB Pending and Project Status is In progress, locate the project and choose More > Re-evaluate in the Operation column. Evaluation Status shows the current evaluation status and progress, and Project Status is In Progress. You can click Stop or Resume to stop or resume the re-evaluation. This function is not available for DB2 databases.
   Compatibility analysis	Current Dynamic SQL Evaluation Config	The information of incompatible dynamic SQL statements includes the name, default value, validation, unit, and value. It is only available for Oracle databases.
   	Workload Evaluation	When the source database is Oracle, the information includes the DBA workload, development workload, and test and rollout workload.
   	Evaluation Statistics	When the source database is Oracle, the information of supported objects and unsupported objects. Supported objects include native-supported objects, UGO-supported objects, and supported objects with risks Move the cursor to the icon to view the conversion details. Click View details to view supported objects with risks and unsupported objects. Click Report on Partially Compatible and Unsupported Objects. This report includes all source SQL statements and details on any syntax conversion failures. Click Anonymous Report on Partially Compatible and Unsupported Objects. This report includes all source SQL statements and details about any failure points in the SQL statements, but the statements will be anonymized. The actual syntax will not be exposed.
   	Partially Compatible/Unsupported Syntax	All partially compatible or unsupported syntax points during database object conversion are displayed. The detailed information includes Partially Compatible/Unsupported Syntax, Object Scope, Type (not supported or partially compatible syntax points), Risk Level (risk level of partially compatible syntax points), Count (number of occurrences of a syntax point), and Operation (You can view definition of syntax points). Locate a syntax point and click View Definition in the Operation column to view its analysis and explanation. If a syntax point type is partially compatible, UGO provides the different conversion configuration items of the syntax point. During the migration, you can select a configuration item as needed. If no modification suggestion is provided, you can click the syntax point name to view details. This function is not available for DB2 databases.
   	System Objects	The page displays the types of system objects, occurrence count, and compatibility if the target database is GaussDB. Click System Objects Report to download the report to the local PC. The report provides detailed analysis of system objects in the application system, including the object name, occurrence times, and compatibility description. This function is not available for DB2 databases.

The source database syntax is complex and flexible, so the workload evaluation and object evaluation statistics are for reference only.