Jenner is an independent engine for the SAS language. It runs your DATA steps, PROCs and macros inside your Databricks workspace, on the tables you already have, so a move to Databricks does not have to start with a rewrite.
Yes, with Jenner. Install the Jenner package from a Unity Catalog volume, load it in a notebook, and put SAS code in a %%jenner cell next to your Python and SQL cells. Name the tables the program reads with --in and the tables it writes with --out. The same program can also run as a task in a Databricks job.
The language does not need translating. Most programs do need their file and library paths pointed at Databricks locations, because a program that reads /sasdata/sales has to be pointed at a volume or a table instead.
Jenner is one engine. In Databricks it runs on your serverless compute, under your Unity Catalog permissions.
Put a SAS program in a %%jenner cell. The listing and the log appear below the cell, and WORK data sets carry over from one cell to the next for the rest of the session.
Run a .sas file as a task in a Databricks job with the jenner-run entry point, on the schedules you already use. Each run keeps its program, log and listing in a run folder on a volume.
--in reads a table, or a temporary view of a DataFrame, as a SAS data set. --out writes a data set to a Delta table: it replaces the rows, appends them, or refuses if the table exists. Columns keep the table's types, and nothing is cast silently.
A permanent SAS library is kept as Parquet files on a Unity Catalog volume. Each run's program, log, listing and output files are copied to the user's own storage on a volume, so they outlast the serverless machine.
It is the same engine that runs on Linux, macOS and Windows, packaged for Databricks. Procedures that need R cannot run on serverless compute, which has no R; they stop with a clear error.
Jenner runs on your Databricks compute and reads your tables under your Unity Catalog permissions, so your data stays in your workspace.
By default each user gets a volume of their own for their WORK library, their JENUSER library and the logs, listings and files of their runs. Only that user, your metastore admins and the owners of the catalog and schema can read it.
An administrator can choose one shared volume with a folder for each user instead. Every Jenner user can then read every other user's files, and the Jenner App says so before the switch.
A workspace administrator installs the Jenner App in Databricks. It shows the licence status, installs and renews the licence key on a volume, and sends a monthly usage report. To buy, the administrator opens the Jenner website from the App and pays by card.
Your workspace ID and host, the cloud, the App version, the licence serial number, monthly counts of active users with salted hashes of their identities, and the administrator's email address at checkout. It does not send your tables or your SAS programs.
Jenner Studio is coming to Databricks. It is not available there yet.
The Jenner listing on Databricks Marketplace is on its way. Ask for early access and we will get back to you.
Request early accessTell us roughly how many SAS programs you run, how often, and which procedures matter most.