Every environment is different
Results shown here come from a synthetic SQL Server test database. Running SQL2Snow against your environment produces findings based on the database objects and migration patterns it detects.
Actual SQL2Snow output from a synthetic SQL Server environment.
Migration Complexity · Estimated Effort · Complexity Drivers · Recommendations
SQL2Snow Migration Assessment Report
Synthetic SQL Server test database · Generated by SQL2Snow Community Edition
Migration Complexity Score
High Complexity
Why this score?
MERGE statements and dynamic SQL add technical complexity.
Row-by-row cursor logic must be replaced with set-based SQL.
Cross-database references increase integration complexity.
Estimated Effort
220 Days
Estimated effort for initial migration wave
142 – 298 Days
Estimated Range (Low – High)
Effort at a glance
Schema Migration
2 Days
Views
11 Days
SPs and UDFs
159 Days
DB-Level Overheads
2 Days
Testing & Validation
43 Days
Infrastructure & Setup
4 Days
This database has 74 scored objects with overall high complexity. Migration complexity score is 77/100, indicating significant migration effort.
Complexity Breakdown
LOW
Straightforward migration
26 objects
35.1%
MEDIUM
Some planning and effort required
11 objects
14.9%
HIGH
Significant technical challenges
37 objects
50.0%
Complexity Drivers
Count by Impact
56
High Impact
MERGE Statement Semantics, Cursor-Based Processing, Cross-Database Dependencies
149
Medium Impact
Temporary Table Usage, Custom Error Raising (RAISERROR/THROW), SQL Server Error Handling (TRY/CATCH), XML Processing Logic, Encrypted module, Encrypted Objects
Effort Breakdown Details
Directional estimate for initial enterprise migration wave
| Workstream | Min | Max |
|---|---|---|
| Schema Migration | 2 | 3 |
| Views | 7 | 15 |
| SPs and UDFs | 102 | 215 |
| DB-Level Overheads | 1 | 2 |
| Testing & Validation | 28 | 58 |
| Infrastructure & Setup | 3 | 5 |
| Total Estimated Effort | 142 | 298 |
Estimates assume high migration effort. 1 engineer-day = 8 hours. Testing overhead is 25% of object conversion effort.
Object Inventory
Summary of scanned database objects
32Tables
17Views
41Stored
Procs
Procs
16UDFs
7Triggers
41Indexes
83Constraints
8User
Defined Types
Defined Types
Total Objects Scanned: 106
Top Complexity Drivers
Key factors contributing to migration complexity
Complexity driver
Impact
Found in
MERGE Statement
High
14 procedures
Cursor Usage
High
20 procedures
Cross-Database Reference
High
13 procedures and 6 views and 3 functions
Temp Table Usage
Medium
23 procedures
RAISERROR/THROW
Medium
38 procedures
TRY...CATCH Block
Medium
38 procedures
XML Processing
Medium
28 procedures and 11 views and 1 function
Encrypted module
Medium
2 procedures and 2 views and 1 function
Recommendations
Representative actions generated from the assessment findings
High
Validate Each MERGE Statement Against Snowflake Semantics
Review all 14 MERGE statement(s) individually. Pay particular attention to NOT MATCHED BY SOURCE clauses, multi-row targets, and WHEN conditions. Run a proof-of-concept conversion on the most complex MERGE before committing to the full migration approach.
High
Resolve Cross-Database Dependencies in a Pre-Migration Sprint
Identify all 22 object(s) referencing other databases and map each dependency to its target Snowflake account or schema. Design a data-sharing or ingestion strategy for each dependency before the main migration wave begins. Unresolved cross-database references are the most common cause of migration delays.
Medium
Replace Temporary Tables with Snowflake-Native Constructs
23 object(s) use temporary tables. Evaluate each usage and replace with a CTE where possible; use transient or staging tables where intermediate persistence is required. Avoid patterns that rely on cross-procedure temp table visibility, which is not supported in Snowflake.
Medium
Target High-Complexity Objects Early in the Migration Wave
Assign 37 high-complexity object(s) to senior engineers at the start of the migration. Early conversion reduces schedule uncertainty and surfaces design issues while remediation options are still available.
Ready to see your own migration assessment?
Run SQL2Snow locally against your SQL Server environment to generate your own migration assessment.