How to Run SAS Code on Windows

SAS itself runs on Windows. What it needs is a license, and that is usually the part that stops you. Jenner runs the same programs — the same DATA steps, the same macros, the same PROC calls — on the Windows machine you already have, without one.

The short answer

Install Jenner, open a program you already have, and run it. Nothing is converted and nothing is ported: the .sas file on your disk is the file that executes. If you are weighing the options rather than ready to install, the questions further down name every route a Windows user actually has, including the ones that are not us.

It fits the way Windows work already happens

Run a program from the command line so it can be scheduled by Task Scheduler, call it over HTTP from a pipeline, or work interactively in a Jupyter notebook. Programs stay in SAS syntax, so a file written here runs unchanged on a colleague's Mac or on a Linux server.

What runs on Windows

Jenner is SAS-compatible: the language your programs are already written in, running on Windows with the same statement and option names you use now.

DATA steps, PROC SQL, and macros

The core of the language runs as written — DATA step logic, arrays, formats and informats, the macro facility, and PROC SQL. Code that was written against SAS 9.4 syntax does not need a porting pass before it will execute.

100 procedures

Regression and linear modeling, survival analysis, multivariate methods and clustering, time series, quality control, summary and reporting. Every procedure has a published reference page listing the statements and options it supports, so you can check a specific one before committing to anything.

The files already on your network drive

Jenner reads and writes SAS7BDAT and XPT directly on Windows, alongside CSV and Parquet. Datasets sitting on a shared drive do not need converting before you can read them, and output can be written back in the same format the rest of your team expects.

The same program on the server

The same source runs on Windows, macOS, and Linux. A program developed on a Windows laptop runs unchanged as a scheduled job on a Linux server, which is usually where the production run happens.

Results you can demonstrate

Jenner passes all 58 datasets in the NIST Statistical Reference Datasets benchmark — the standard third-party accuracy suite for statistical software. The procedure reference is published in full, so the claim that a specific PROC is supported is one you can check before you migrate anything.

Start Free TrialSee the procedure reference

Frequently Asked Questions

Install Jenner and run the file. It is an independent implementation of the SAS language, so it executes .sas programs directly on Windows without SAS being installed and without a SAS license. The file is not converted first — the program on your disk is the program that runs.

Yes. Unlike macOS on Apple silicon, Windows is a supported platform for SAS 9.4, so this is not an architecture problem. The obstacle for most people is the license and the approval to install it, not whether the software can run.

Jenner runs on Windows 11 and Windows 10. For SAS 9.4 itself, supported operating-system versions are set by SAS and change between releases, so check their documentation for the release you hold rather than trusting a third party on it.

No. Jenner is a clean-room implementation of the SAS language and does not embed, wrap, or call SAS software. It needs no SAS license at any layer, and there is nothing to check out or renew.

Point the Jenner executable at a .sas file and it runs, writing a log and any output datasets where you ask for them. Because it is an ordinary command-line program, Task Scheduler, a batch file, or a CI runner can invoke it the same way they invoke anything else.

No. Programs stay in SAS syntax — the same DATA steps, macros, and PROC calls you have now. Coverage is not the whole language, so the honest way to judge your own code is to run it and read the log rather than take a general claim on trust.

Yes. Jenner reads SAS7BDAT and XPT directly, and can write them back out or convert them to CSV or Parquet. That works whether or not the file was produced by SAS, and whether it is on your disk or a shared drive.

SAS OnDemand for Academics is free, runs in a browser on Windows, and is the right choice for teaching, learning and research — SAS restricts it to academic use, so it is not a route for commercial work. It also runs on SAS's infrastructure rather than your machine, which matters if your data cannot leave your network.

Altair SLC also runs SAS-language programs without a SAS license and has been doing it far longer than we have. If you want a vendor with a long track record on your exact edge case, it is a serious option and you should price both. We would rather you chose deliberately than found out later. Siemens now sells it as Rapidminer SLC, so it is worth searching under both names.

Sometimes yes. If the code is small, or already being rewritten, or the team is moving off SAS skills anyway, then porting to Python or R is the better end state and you should do that instead. The case for running the SAS code is strongest when there is a lot of it, it is validated, and rewriting it means re-validating it.

Run your SAS programs on Windows

No SAS license, and no rewrite. The same programs you already have.

Start Free Trial