CAST HIGHLIGHT - Results - SQL file analysis is not generating results – CAST

Analysis of some SQL files are not generating any results.

Also there are no messages in the logs.

Only one SQL file which contains procedures scanned fine.

Even when upload was attempted through CLI there are no results in the HL portal.

Details

This is an expected behavior.

Check if the specific SQL technology is supported. For eg, if the SQL code that is analyzed is MySQL it is expected to not see scores for Software Health and Cloud Maturity insights as MySQL is not supported. But MySQL is supported for Software Composition, Detection and Sizing metrics etc. For more details please refer https://doc.casthighlight.com/#technologycoverage or --printTechnos in CLI to print the supported technologies.
The non-procedural part of SQL code is excluded from the analysis. Nothing is done with embedded code, that is SQL code located inside the application code (Java, C# etc). Only procedural code located in files with the appropriate extension are analyzed.
Rename the .SQL with appropriate technology extension. Detailed information can be seen in Getting-Started-Guide.pdf
1. CAST database extractors produce .src by default. However, you can easily rename file extensions.
2. Change the extension from .sql to .psql, files as it will associate the files to the PL/SQL analyzer.
3. Check if the sql is written on mysql, if yes please use .tsql extension.
4. Check if T-SQL Specific syntax is there, such as commas as the terminators then it should have .tsql extension.
If the file contains ALTER PROCEDURE and ALTER TRIGGER statements, then it may be skipped from analysis as Alter syntax is not supported. Statements with CREATE gets analyzed as it is supported. Please refer CAST HIGHLIGHT - Analyzer -The database objects Highlight takes into account
For different technology, scan can be run with --technology. --technologies (optional) Technologies you want to explicitly scan in your sources. Separated by "," Check the CLI options in Highlight Automated Code Scan (Command Line)
Check the logs if there are other reasons such as file size etc which is preventing the scan from happening. Please refer CAST HIGHLIGHT - Discovery Step - .sql Files not getting scanned because of file size and CAST HIGHLIGHT - Discovery Step - Analyzer not detecting all the technologies