Snowflake
Snowflake migration from Oracle, SQL Server, MySQL, MariaDB
Last updated:
Datalobe migrates Oracle Database, SQL Server, MySQL and MariaDB to Snowflake: it assesses the source, compiles and checks every converted object on Snowflake before deploy, loads data in batches with change data capture (CDC) until cut-over, and validates every table with 17 checks.
Source
Oracle Database
SQL Server
MySQL
MariaDB
Target
Snowflake
- Code
- Snowflake Scripting
Conversion
What converts to Snowflake?
Here is what each source object becomes on Snowflake.
| Source object | Snowflake result |
|---|---|
| Stored procedures (T-SQL or PL/SQL) | Snowflake Scripting procedures |
| Views | Snowflake views |
| Tables and data | Snowflake tables |
Snowflake Scripting is Snowflake's procedural language for stored procedures. AI converts stored code, every AI conversion is checked, and anything that cannot be proven goes to a named person.
Every converted statement is compiled and checked on Snowflake before deploy.
Example run
DW-SQLServer to Snowflake-Analytics in numbers
In the example run, SQL Server 2022 database EDW moved to Snowflake database ANALYTICS on 30 Sep 2026.
- Tables
- 640
- Rows
- 3,812,440,906
- Verdict
- Passed
Validation
Why does validation matter for analytics migrations?
A warehouse migration can load cleanly and still be wrong, so every table gets 17 checks in six groups.
Questions
Frequently asked questions
Can SQL Server stored procedures run on Snowflake?
Not as they are. Datalobe converts them to Snowflake Scripting. In the example run, 184 stored procedures converted this way.
Can Oracle Database migrate to Snowflake with Datalobe?
Yes. Oracle Database, SQL Server, MySQL and MariaDB are all supported sources for Snowflake.
How do you prove the warehouse numbers match the source?
Validation runs 17 checks per table, including row counts and checksums on all rows, and compares sample rows value by value. The Validation Report shows the evidence for each table.
Can we keep using the source during the migration?
Yes. CDC keeps Snowflake in sync with the source until you cut over. With keep-in-sync (CDC), downtime is limited to the cut-over window.
Sources (10)
- Snowflake Documentation Developer Guide: Snowflake Scripting Developer Guide, checked
- Snowflake Documentation Developer Guide: Writing stored procedures in Snowflake Scripting, checked
- Snowflake Documentation Developer Guide: Stored procedures overview, checked
- Snowflake Documentation SQL Command Reference: CREATE VIEW, checked
- Snowflake Documentation SQL Command Reference: CREATE TABLE, checked
- Snowflake Documentation SQL Command Reference: COPY INTO <table>, checked
- Snowflake Documentation SQL Function Reference: TO_DECIMAL, TO_NUMBER, TO_NUMERIC, checked
- Snowflake Documentation SQL Data Types Reference: Numeric data types, checked
- Oracle Database 19c PL/SQL Language Reference, checked
- SQL Server Transact-SQL Reference: CREATE PROCEDURE (Transact-SQL), checked
Next step
Plan your Snowflake migration
Start with an Assessment Report on your source database.