Issues Report

This is a deprecated version of the SnowConvert documentation, please visit the official site HERE.

Every SnowConvert run will generate a file named Issues{timestamp}.csv, which contains some important information about the error, warnings, and information messages that are generated during the migration. Example:

SessionID	EWI Severity	EWI Code	Name	Description	Parent File	Line	Column	Database Name	Schema Name	Package Name	Object Name	Object ID	Object Type	Object Size
Not available	Low	MSCEWI1050	Missing Dependencies Objects	MISSING DEPENDENT OBJECT "missing.object1"	sample.sql	80	43			N/A	teradata_table_s	teradata_table_s	TABLE	S
Not available	Medium	MSCEWI1073	Pending Functional Equilavalence Review	PENDING FUNCTIONAL EQUIVALENCE REVIEW FOR 'FNC' NODE	sample.sql	35	6			N/A	teradata_view_xs	teradata_view_xs	VIEW	XS
Not available	Low	MSCEWI2025	Output format not supported	OUTPUT FORMAT 'MMDDYYYY' NOT SUPPORTED.	sample.sql	45	20			N/A	teradata_function_xs	teradata_function_xs	FUNCTION	XS

Here are all the columns of the report:

1. SessionID

   • A unique identifier of the migration id.

2. EWI Severity

   • One of the following values: Critical, High, Medium, Low, or None. This is an indicator of how much effort it takes to manually solve the problem. Severities Critical, High, and Medium punish the conversion rate.

3. EWI Code

   • A unique identifier for the EWI.

4. Name

   • The name of the EWI message.

5. Description

   • The final message printed to the output files. There are multiple possible descriptions for a single EWI Code. For example, MSCEWI1036 is used to indicate that a specific data type in the original platform is converted to another yet functionally-equivalent data type in Snowflake. So, the following are all possible descriptions for this EWI.

   
   /*** MSC-WARNING - MSCEWI1036 - INTERVAL DATA TYPE "YEAR(2)" CONVERTED TO VARCHAR ***/
   /*** MSC-WARNING - MSCEWI1036 - INTERVAL DATA TYPE "MONTH(2)" CONVERTED TO VARCHAR ***/
   /*** MSC-WARNING - MSCEWI1036 - XMLTYPE DATA TYPE "SYS.XMLTYPE" CONVERTED TO VARIANT ***/

6. Parent File

   • The relative path of the file where the EWI is generated.

7. Line

   • The text line within the parent file where the EWI is generated.

8. Column

   1. The column within the line where the EWI is generated.

9. Database Name

   • The database name (if applicable) of the object that contains the EWI. It might be empty because of multiple reasons, such as:

     1. The object containing the EWI has no explicit database name.

     2. The EWI is not generated within an object but another SQL element, such as a DROP, UPDATE, or SELECT statements that are not part of any object.

10. Schema Name

    • The schema name (if applicable) of the object that contains the EWI. It might be empty because of multiple reasons, such as:

      1. The object containing the EWI has no explicit schema name.

      2. The EWI is not generated within an object but another SQL element, such as a DROP, UPDATE, or SELECT statements that are not part of any object.

11. Package Name

    • The package name (if applicable) of the object that contains the EWI. It might be empty because of multiple reasons, such as:

      1. The object containing the EWI has no explicit schema name.

      2. The EWI is not generated within an object but another SQL element, such as a DROP, UPDATE, or SELECT statements that are not part of any object.

12. Object Name

    • The name of the object, without database and or schema qualification.

13. Object Id

    • A string that uniquely identifies the object.

14. Object Type

    • The type of object in which the EWI is generated, such as TABLE, VIEW, PROCEDURE. It might be empty if the EWI is generated within another SQL element.

15. Object Size

    • A size classification of the object, based on its line of code. The available measurements are XS, S, M, L, and XL.