BookmarkSubscribeRSS Feed
DataFriend
Calcite | Level 5

My disk space on my lap top fills up quickly when running commands in SAS a few times causing my computer to crash as well as the application.  I log in through docker desktop.

 

1 REPLY 1
ballardw
Super User

Note that if you are crashing SAS then it is not cleaning up temporary space properly and that means that you have less when you start. There can be a lot of "stuff" there.

You can run this code to find your current Work library location and delete the other temporary libraries using operating system tools to help get rid of those files.

 

proc options option=work;
run;

On my system today that shows this result in the LOG:

 WORK=C:\Users\Owner\AppData\Local\Temp\SAS Temporary
Files\_TD5172_DESKTOP-C36D7SF_

So I would look in C:\Users\Owner\AppData\Local\Temp\SAS Temporary Files and delete any of the other folders and their contents that start with _TD to get rid of left over files.

 

I would also check to see how much space you have on your drive. If you are running out space frequently I would suspect something else is using a lot of space and may be time to delete some of those cute kitten videos (or what ever is using the space).

 

Note that not just data sets but the displayed output from the results window is written somewhere, usually the work library. So anything that generates lots of output such as proc freq on a large data set with lots of values can eat up a lot of space.

 

What exactly are you attempting to do, as in code, when you fill up your drive?

 

hackathon24-white-horiz.png

The 2025 SAS Hackathon Kicks Off on June 11!

Watch the live Hackathon Kickoff to get all the essential information about the SAS Hackathon—including how to join, how to participate, and expert tips for success.

YouTube LinkedIn

Mastering the WHERE Clause in PROC SQL

SAS' Charu Shankar shares her PROC SQL expertise by showing you how to master the WHERE clause using real winter weather data.

Find more tutorials on the SAS Users YouTube channel.

Discussion stats
  • 1 reply
  • 450 views
  • 1 like
  • 2 in conversation