【SAS Series】 Introduction to SAS Studio and Account Setup

"I honestly thought I’d never touch SAS again in this lifetime, and yet here I am—dragged back into it."

Published on: 2025/12/25

---

Introduction

Why did I suddenly decide to start writing SAS technical content?

I always thought I’d left SAS behind for good. After switching from public health to law and starting over from scratch, SAS gradually faded from my life.

All my programming skills were basically useless in the face of issue spotting, three‑step legal reasoning, and doctrinal analysis.

Back then I imagined I’d just keep working in the legal field and pretend those technical skills didn’t exist.

But last year, I heard IQVIA was looking for cross‑disciplinary SAS programmers in Asia, and through a series of coincidences I ended up back in the biomedical industry, joining the Real World Solutions team as a SAS programmer.

During college, I had almost nothing to do with clinical trials. My background is in environmental and occupational health, and even after moving into law I focused on labor law.

My only real connection to clinical trials is SAS programming—that’s the skill that brought me into this field.

Back when I was learning statistics and SAS in college, I already wanted to turn my learning process and pain points into structured notes.

I didn’t do it then partly because I didn’t feel I had the right “identity,” and partly because I didn’t have a good platform.

Now I have both—a relevant role and this website—so it feels like the right time to finally start organizing everything.

How long will this series go on? I honestly don’t know. Let’s just see where it takes us (totally non‑committal mode).

What I want this series to be

When I started thinking about this series, I asked myself: with so many SAS articles and videos already online, what kind of role do I want my content to play in this crowded space?

In English, there are already tons of resources—articles, videos, and other supporting materials for SAS programming and data analysis.

But in Traditional Chinese, the resources are fewer, sometimes outdated, and often I had to switch to English references whenever I wanted to look up a specific function. That felt like a pity.

So my goal is to build a detailed, step‑by‑step introduction to SAS that helps beginners get comfortable, instead of just copying and pasting TA’s code in biostatistics class without understanding what’s going on.

Of course, SAS Help is extremely comprehensive, but it can be overwhelming and hard to navigate for everyday users, and the key points are easy to miss.

The target readers aren’t people who have never heard of SAS at all, but those who already have some sense of what SAS is, yet feel their programming structure is incomplete or fuzzy.

So this series is essentially my own learning notes from when I first picked up SAS, plus common issues I’ve faced in real‑world work.

Before diving into syntax and architecture, this first article focuses on the SAS Studio environment itself—making sure you can log in, see the interface, and roughly understand what each window does.

Once we get to syntax and program structure in later articles, you’ll be able to try things out instead of just reading about theory.

I’ll also weave in key points from studying for the SAS Base and SAS Advanced exams, as well as notes from books I used when preparing for my IQVIA SAS programmer interview.

So yes, this will basically be a big collection of mixed‑type notes.

The order of topics may not always be strictly linear—it’ll be more like “I write what I feel like writing.” If you need something specific, you might have to search around a bit; fair warning up front.

That said, I’ll try to keep the foundational knowledge articles in a reasonably logical order at the beginning.

One more thing to clarify: although SAS is a powerful statistical analysis tool, this series will not delve into statistical theory unless absolutely necessary. The focus is on SAS programming and data handling, not on teaching statistics itself.

If there are particular topics or small projects you’d like to see—whether related to clinical trial data, education analytics, or even escape room‑style data puzzles—you’re very welcome to email me with suggestions : D

Why SAS Studio?

I personally work with three SAS environments: SAS Base, SAS Enterprise Guide (EG), and SAS Studio.

Although they differ in how they run internally and how the interface looks, the coding part is largely similar.

Compared with Base, SAS EG and SAS Studio have more user‑friendly graphical interfaces.

I first learned SAS using the school’s SAS Base installation. But since I’ve graduated for some years now, I no longer have a way to get a licensed Base setup through academia.

My company uses SAS EG, but that’s a company resource, and I shouldn’t use it for personal content like this series.

That leaves SAS Studio as the ideal choice: it’s free, cloud‑based, and all you need is an internet connection.

So in this article we’ll focus on two main things: how to get a SAS Studio account, and an overview of the basic interface and operations.

SAS Studio Account Setup

SAS Studio runs through a web browser. You write code in the browser, and it’s sent to a SAS server in the cloud for processing, then the results are returned to your screen [1].

You must first create an account before you can access your personal SAS Studio workspace.

So in this section we’ll walk through how to sign up for a SAS Studio account.

You can go directly to the following website to start the account registration process:

SAS Studio page

Later on, you’ll also use this same page to log in. But for now, since you don’t have an account yet, scroll down the page and look for “Get Started,” then find “SAS Profile” (the red box in the screenshot).

Fill in your information on the profile registration page.

For the language setting, once you select a language, the page automatically switches to that language—which is quite user‑friendly.

After filling everything out, click the button at the bottom to submit. If you’re using the Traditional Chinese interface, the button will say “建立個人認證帳戶” (Create personal profile).

The next step is email verification. SAS will send an email to the address you provided.

In the email, you’ll see a link like “Activate your SAS Profile.” Click it, and a new page will open asking you to set a password.

Note that the SAS Studio password must be at least 8 characters and include uppercase letters, lowercase letters, numbers, and symbols.

Once you see this page, your SAS Profile has been created.

After your profile is created, go back to the original SAS OnDemand page. In the top‑right corner, click “Sign In.”

Are we ready to use SAS Studio now? Not quite.

Even with a SAS Profile, you still need to register for SAS OnDemand. When you sign in, you’ll see the popup shown above.

Check the box in the highlighted area and click “Register.”

Next, you’ll be asked to choose a server location. Since we’re using a Chinese interface, “Asia Pacific” is the appropriate choice.

Because the server location cannot be changed later, there is an extra confirmation step.

Once you receive this email, your account is fully registered. You can then return to the SAS OnDemand page and log in to SAS Studio using your User ID or email address.

After logging in to SAS OnDemand, you’ll see the screen above. Click “Launch” to open SAS Studio.

If you can’t log in immediately, give it a bit of time—the system sometimes needs a moment to update.

If you see this interface, it means you have successfully entered the SAS Studio environment.

SAS Studio Interface Overview

To make the explanation easier, I wrote a small example program here. Using a DATA Statement, I entered some sample data, then used a PROC Statement to generate basic results.

CODE tab and program name

The place where you actually write SAS code is under the Code tab—the area highlighted in the red box below.

We’ll talk about SAS syntax and program structure in other articles. For now, just get familiar with where the key windows are and what they do.

The label “Program 1.sas” on the Code tab is the name of your SAS program file.

SAS programs are saved with the “.sas” extension.

Although SAS Studio runs in the cloud, different users log in with separate accounts, so your programs can be stored in your own cloud workspace.

If you want to save a program you’ve been working on, click the icon inside the red box in the screenshot below.

Personally, if a program is important, I recommend downloading a copy and keeping it on your own computer as backup.

To run the program, click the small black “Run” icon highlighted below.

LOG tab and how to read it

After running code, the Log tab shows execution details: how long the program took to run, whether there were errors or warnings, and more.

We’ll talk about common types of errors and how to interpret SAS logs in future articles.

RESULTS tab and output

If your program produces output tables or reports, SAS Studio displays them under the Results tab.

In my example, I requested basic statistics for variables A, B, C, and D, so SAS generated corresponding summary tables.

These tables are stored under Results.

OUTPUT DATA tab and generated output datasets

If your program includes a DATA Statement, or certain code that produces output datasets, those datasets will appear under the Output Data tab.

If no such datasets are generated in a given run, this tab will not appear.

In our example, we used a DATA Statement to input several variables and named the dataset test, so it appears as an output dataset here.

If you want to see variable attributes for an output dataset—such as length, type (character or numeric), and so on—you can click the Table Properties button to view them all at once.

Left sidebar and key functions

On the left sidebar, the two most important sections are “Server Files and Folders” and “Libraries.”

Under “Server Files and Folders,” Files(Home) holds files stored on the server. For example, if you save a program, it will appear here.

Files placed in Files(Home) can be downloaded to your local computer. We’ll come back to this later in the article.

The Libraries section works just like Libraries in traditional SAS environments.

If you’ve used SAS EG or SAS Base, you’ll notice the Libraries structure is similar—they all share the same built‑in libraries.

Generally, if you run a DATA Statement without explicitly assigning a library for the output dataset, SAS stores the result in the Work library by default.

In our example, the dataset test created by our code also appears under Work, as shown in the screenshot.

Importing External Data into SAS Studio

Putting the analysis methods aside for a moment—what if you already have a data file and want to bring it into SAS Studio?

In traditional SAS Base or EG, you usually know the folder structure clearly, so you can import data using code and file paths.

But because SAS Studio runs in the cloud, the folder structure is less intuitive. So here I’ll show you the method I use most often.

The steps are:

Step 1: Upload the data file you want to analyze into Files(Home).

Step 2: Use the SAS Studio‑generated code to import that file into the Work library.

Upload to Files(Home)

On the left sidebar, find “Server Files and Folders,” then click “Upload” in the toolbar above.

After clicking Upload, a popup appears where you can choose which file to upload and where to place it.

The destination path is on the SAS Studio cloud server.

After selecting the file, you’ll see it appear inside the Files(Home) folder.

Loading the data file into the Work library

Double‑click the uploaded file, and SAS Studio will open it in the right pane.

Then select the Code tab—SAS Studio will automatically generate code to import this file into the Work library.

Select this block of code and click the black Run icon. The file will then be imported into Work.

If you want to rename the dataset, change the name IMPORT inside “%web_drop_table(WORK.IMPORT);” to another name.

Once imported, you can reference this dataset in subsequent DATA or PROC Statements for data cleaning or analysis.

Exporting Data Processed in SAS Studio

Data processed in SAS can generally be exported in two ways: as Results (reports) or as datasets.

Exporting via RESULTS

Program output—such as statistical tables—appears under the Results tab.

Within this tab, there are multiple ways to export your results—for example, saving as HTML, printing, and more.

Of course, you could also manually copy the numbers into a spreadsheet if you don’t mind the extra effort XD.

Exporting as a dataset

If you don’t want to copy values by hand, or you need the results for further analysis in CSV or Excel format, you’ll need to export them as datasets.

The way to convert PROC output into datasets varies by procedure—each PROC Statement may have its own options.

We’ll get into the details of this in other articles when we talk about specific procedures.

Right‑click the dataset you want to export, then select Export.

Just like importing, to download a dataset you must first export it into Files(Home) and then download from there.

Select Export, choose the file format (e.g., CSV or XLSX) and file name, and set the destination path to Files(Home).

Once the exported file appears under “Server Files and Folders,” you can click the download icon to save it to your computer.

Conclusion

I had no experience with SAS Studio until my company required SAS certification and I realized I no longer had access to SAS Base, nor could I use EG for personal learning. That’s when I started learning this new environment.

In practice, aside from the cloud interface and slightly more involved import/export steps, SAS Studio is very similar to Base and EG. The coding itself hardly changes.

If you want to learn and practice SAS programming, SAS Studio is an excellent, free option that doesn’t rely on school licenses.

This article briefly introduced SAS Studio account setup, the main windows, and how to import and export data. Although it touches on topics we’ll expand on later, for now just get a general sense of the flow—programming details will come in future articles.

As the opening piece of this series, it also explains who this content is for, what it aims to offer, and why I’m writing it.

On a personal level, I also hope that through writing, I can keep my own writing muscles active and continue growing as a SAS programmer.

In the next article, we’ll look at basic SAS syntax rules and introduce the simulated dataset we’ll be using throughout the series.

See you in the next article : D.

References

[1] Introduction to Programming: SAS® Studio 3.4, SAS Institute Inc.

FAQ

You might also be interested in these articles

堪稱奇幻旅程的IQVIA的SAS programmer面試和錄取經驗分享

IQVIA上工一個月左右的小記錄與心得

【SAS Series】 The First Step for SAS Beginners: Core SAS Rules and the Clinical Trial Dataset Used in This Series