BookmarkSubscribeRSS Feed
tsndrct1234
Obsidian | Level 7

Hello SAS Community!

 

I need your help estimating the additional workspace I should add on our SAS work. Currently I'm running a huge job on SAS EG that tries to join two huge table with roughly 9M and 5M records via Proc SQL and it causes I/O Error.

 

tsndrct1234_0-1662450018891.png

 

Do you have any rough estimate how much additional space I should request? Also, it's 75% of the flow I'm currently running so there would be upcoming jobs that needs to be executed and it might still use SAS work.

 

Thank you so much for your help!

 

5 REPLIES 5
Ksharp
Super User
Change your WOKR library path into another to make enough room for WORK library, like : D:\TEMP\

You can change it ,by add the following option into SASV9.CFG file.

-WORK "D:\TEMP\"
Astounding
PROC Star

It is difficult to believe that you have use for an output table with 45 trillion rows in it. 

 

Perhaps if you were to provide some details of the SQL code and what you plan to do with the results, there might be suggestions about other ways to approach the problem.

Kurt_Bremser
Super User

Please show your SQL code.

Also tell us more about the relationships between the two tables with regards to the key(s). If you have anything but many-to-many, sorting and a data step MERGE will be more efficient.

Sajid01
Meteorite | Level 14

Often inefficient or incorrect SAS code some times result in large util files and the temporary work space gets filled up.  All running codes get impacted. This results in this type of errors.
Reach out to your SAS Administrator for assistance and investigation.

Patrick
Opal | Level 21

Before considering to increase the disk space for WORK I'd be verifying two things

1. How much space would this SQL require? Is it eventually some badly formulated code that results in a cartesian join between two big tables?

2. Are there old Work spaces that haven't been cleaned-out? Are you regularly running cleanwork?

 

From a coding perspective

If you're creating big work tables then eventually delete them in your process scripted when no longer required (proc datasets/delete).

 

Depending on your usage of SAS you might also consider to point Work and Utilloc to different disks. But always ensure that these are disk with as much I/O as you can get.

Ready to join fellow brilliant minds for the SAS Hackathon?

Build your skills. Make connections. Enjoy creative freedom. Maybe change the world. Registration is now open through August 30th. Visit the SAS Hackathon homepage.

Register today!
SAS Enterprise Guide vs. SAS Studio

What’s the difference between SAS Enterprise Guide and SAS Studio? How are they similar? Just ask SAS’ Danny Modlin.

Find more tutorials on the SAS Users YouTube channel.

Click image to register for webinarClick image to register for webinar

Classroom Training Available!

Select SAS Training centers are offering in-person courses. View upcoming courses for:

View all other training opportunities.

Discussion stats
  • 5 replies
  • 507 views
  • 0 likes
  • 6 in conversation