SnowConvert AI - Reports

用語集

このセクションでは、 SnowConvert によって生成される複数のレポートドキュメントで使用される概念について説明します。

  • Lines of Code (LOC): the total number of lines in the text of the source code files, excluding blank lines, that were processed by the conversion tool. A comment is considered a line of code.

  • Parsing EWIs: the total count of parsing errors that occurred during the code analysis process. A parsing error occurs when the parser (the component that reads and understands the source code files) encounters something unexpected. This usually means a syntax error, which refers to a code element in the file that did not match the SQL grammar specification that the parser was expecting. In other cases, these errors can also occur because the parser is not yet ready to support a specific grammar. Parsing errors are considered critical issues because if the code is not parsed, SnowConvert AI cannot assess it or translate it. If this number is high in relation to the migration workload size, input code revision is advised.

  • Unrecognized Elements: any code element (or parts of them) such as DML, DDL, control statements, with parsing errors that SnowConvert AI was unable to process.

  • Lines of Code in Unrecognized Elements: the total lines of code in all the unrecognized elements. This is a good indicator of how much code SnowConvert AI was not able to process.

  • (Top-Level) Code Units: a Code Unit is the most atomic, standalone executable element. In most cases, these are statements (like DDL or DML), but they also include script files because those are executed as a single element. They are classified as top-level because they are usually the “root” elements for a database dialect, and they can contain other “smaller” definitions. The top-level code units vary from one SQL dialect to another (Oracle, Teradata, SQL Server, etc). Parsing errors might cause SnowConvert AI to not be able to properly count all top-level code units.

  • Lines of Code Conversion Rate: the percentage of lines of code that were successfully converted by SnowConvert AI into Snowflake code. Take into consideration that unrecognized elements (because of parsing issues) will affect this metric, as their source code will be counted as not converted. Furthermore, a successful element conversion might not be fully equivalent in Snowflake because of platform differences or limitations. In these cases, while the conversion rate is not punished, SnowConvert AI will generate an FDM to alert about the possible difference in functionality. A 90% conversion rate for a code unit means that only 10% of its lines of code were not converted, and therefore, EWIs are generated for them.

  • Fully Converted Code Units: the percentage of top-level code units that were fully converted without any error in any of their sub-parts. They are considered ready for deployment. Any code unit whose conversion rate is less than 100% is not counted as fully converted.

評価レポート（docx）

評価レポートは、コード変換率の見積もりや、ユーザーが機能的に等価なSnowflakeコードを達成するまでの距離を見積もるための、その他多くの有用な情報をまとめた文書です。

トップレベルコードユニットレポート

トップレベルコードユニットレポートは、ソースコードに存在する主なオブジェクトの概要を提供します。これらのトップレベルのオブジェクトは、変換の状態に関する有用な情報を持っており、変換の後に次のステップをどうすべきかを決定するために使用することができます。

問題レポート

問題レポートは、移行プロセス中に発生したすべての問題についての情報を含んでいるファイルです。

要素レポート

要素レポートには、移行プロセス中に見つかった文法要素の数が要約されて表示されます。要約は複数列ベースで行われるため、同じ文法要素が異なる文脈に属する場合は区別されます。たとえば、 SELECT クエリは、 PROCEDURE の一部であったり、 VIEW の一部であったり、スクリプトファイルの一部であったりします。このレポートを使用すると、要素を微妙なニュアンスで見ることができ、全体的な変換ステータスを確認できるようになります。

Functions Usage Report

The Functions Usage report summarizes the invocations of built-in and user-defined functions found during the conversion process, grouped by their migration status. This report allows the user to get details about function usages, whether they were transformed to Snowflake with no problem, or whether they require an additional post-conversion action.

言語: 日本語