validate-sas-conversion

Validate SAS to Snowflake Conversion

Dual-execution comparison framework: LLM traces SAS logic to produce expected baselines, then executes converted SQL on Snowflake and compares.

Execution Model

Component	Engine	Snowflake?
Synthetic data generation	LLM + SQL	Yes (temp tables)
SAS logic trace (expected baseline)	LLM	No
Converted SQL execution	Snowflake	Yes
Output comparison	SQL MINUS/EXCEPT	Yes
Artifact persistence	CSV + SQL files to disk	No

Snowflake is used for execution with explicit credit confirmation per Snowflake Interaction Policy.

When to Load

[convert-sas-to-snowflake] Step 8: After user opts to validate conversion, or when user explicitly requests validation of existing converted code.

Arguments

• $CONVERTED_CODE - Path to converted .sql file or SQL code to validate
• $ORIGINAL_SAS - Path to original SAS code (REQUIRED for baseline generation)

Rules

1. Never modify the converted code - Create test wrapper/harness separately
2. Original SAS code is REQUIRED - Cannot generate baseline without it
3. Schema inference - Derive from SQL CREATE statements, SELECT columns, or original SAS
4. Persist all test artifacts - Save synthetic data, expected baselines, actual results, and validation reports to disk subfolders (see Artifact Persistence below)
5. Load reference files - Read references/synthetic-data-rules.md and references/comparison-rules.md before generating data or comparing
6. Snowflake execution - All SQL execution runs on Snowflake with explicit credit confirmation per Snowflake Interaction Policy.

Artifact Persistence

All test artifacts MUST be persisted to disk in the conversion output directory. This enables reproducibility, audit trails, and inclusion in the conversion report.

Directory Structure

Create the following subfolder structure relative to the conversion output directory (same directory as the generated .sql files):