04-27-2017 06:37 AM
We are often running out of available user space within our SAS Grid environment. Meaning space to store files. This is due to the number of users, number of files, and size of files / datasets. I am looking for "best practices" and tips information regarding managing users and files they create. This is to regain available storage space within our SAS Grid. I've searched through the forums but not really found info specific to this.
04-27-2017 06:40 AM
If you use workspace servers, so that every user is recognizable at the OS level, set up quotas for users. This way they run out of individual space before causing a showstopper for everybody else.
04-27-2017 08:27 AM
I subscribe to what @KurtBremser suggests.
Under a wider perspective, your SAS Grid environment is not different from any environment that creates data. A data (big data) environment is created to handle a certain amount of requirements (users, processes, data to be handled, etc), and, therefore, the more demanding environments also require higher specifications and sizing, and to handle larger temporary data.
The first approach would be to separate the resources from the SAS services and batch processes (SAS Stored Process Server SAS Pooled Workspace Server and SAS Batch Server, at least) from the interactive users (SAS Workspace Server, as @KurtBremser said). On this way, you can be totally in control of the batch and server session resources. This goes specially to SASWORK, SASUSER (normally not in use, but, still), MEMSIZE, SORTSIZE, etc.
As of the interactive sessions, those are the most uncontrollable ones, because it is harder to predict what the users will run, and the quality of their own processes (many users don't know much about SAS itself, or SQL, and are not trained to optimize the queries). Therefore you would want to separate their processes from the batch and the basic services, through the settings on the SAS Workspace Server (which applies to every SAS Solution, and most of the products).
Also for the interactive users, and as you have a SAS GRID environment, probably would make sense to create several SAS Application Servers (SASApps), for each of your business or functional units. Probably each of them will have their own budget to buy SAS GRID resources, and then you can set different resources (SASWORK, storage, RAM memory, etc), depending on their allocated budgets for the SAS environment. Then you can set different SAS Workspace Servers (interactive sessions), but also for the batch and server sessions. Of course, those new SASApps, probably you would like to set them up as Grid enabled, otherwise, by default are to run on a single server.
Speaking about documents, you can find many at:
04-28-2017 09:49 AM
I am not a member or part of our SAS Grid admin team. I am working along with our SAS Grid admin team to help clean up "data gone wild" within our server(s). I can pass your suggestions on to them. Right now we receive warning messags from our SAS admin almost weekly regarding user storage space almost filled up.
I was looking more for suggestions / best practices towards setting some ground rules for file maintenance -- and having users be good stewards for maintaining / compressing / deleting the files they create. We are in the process of setting some ground rules for file maintenance. Of course, this depends on the company and I have ideas of my own, but wanted to get input from those in similar situations or from presentations that I may have missed while googling, researching, etc.
04-28-2017 10:58 AM
Users will NEVER, EVER be good stewards of their data. Not even when hell freezes over so hard that the brimstone becomes superconducting.
The only thing that works is force. They will start to see it as their problem only when they are the only ones affected and nobody else has to care for them.
Spoken from decades as sysadmin.
04-28-2017 08:30 PM - edited 04-28-2017 08:33 PM
@alandool - As part of best practice your SAS admins should be running the SAS CLEANWORK utility across your Grid workspace, scheduled daily. Not sure if you are having problems with SAS temporary space as well but worth checking.