Migration · From SAS
From SAS programs to PySpark
Forge reads your Base SAS programs — DATA steps, PROC SQL, macros and includes — and turns them into PySpark notebooks on Cloudera or wherever your Spark runs, in the order their dependencies need.
What Forge migrates
Programs, steps and the links between them
- Programs
- Scanned from your files and read step by step: DATA steps, PROC SQL and macro definitions.
- Dependencies
- Which program produces the datasets another consumes, and which includes which — so the order is known, not guessed.
- Translation
- Each program becomes a PySpark notebook that keeps the program's meaning, not only its syntax.
- Macros
- Detected and flagged for review.
Why a literal translation is not enough
SAS semantics are where translations break
SAS has behaviours that look like SQL and are not. Forge handles the ones that most often change results silently, and flags what it cannot translate with confidence — so a person looks at it before it runs in production.
- Ambiguous links are left out and reported, never guessed
- Notebooks run on your own Spark cluster
Where Forge stops and asks
- Macros are flagged, not expanded: their output depends on how they are called, and that is for a person to confirm.
See it on your own data
We'll set up Qry against a dataset you choose and walk you through it — one hour, no slides.