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.

언어: 한국어