01-13-2016 03:32 AM - edited 01-13-2016 05:09 AM
After using SAS University Edition for a couple of weeks now, I'm running into the two errors:
PROC SQL; UPDATE Data.example SET endyear = 2020 WHERE flag = 1;
01-13-2016 03:51 AM
A solution is finding a fold which has a large space . and specify :
options user='d:\temp\' ;
this option will use d:\temp\ instead of WORK library . and run your code again.
01-13-2016 04:38 AM
Thanks for your reply Xia, but I don't that will work. I'm running it in VirtualBox, and don't I thought that it was not possible to increase the size of the drive. The virtual size and real size are almost equal (10.7GB, 10.4GB), but I don't know how that is possible, as I don't have that much data (~4GB, of which ~3GB of original data that I trimmed down to that 100MB noted above).
It looks to me like all temp files should be deleted somehow, but I don't know how this is possible or even if this is the way to go.
01-13-2016 04:41 AM
Use a datastep to do the update. It has been pointed out the SQL can get quite resource hungry. Now you can either do this two ways, the simplest would be with a datastep:
data have; startyear=2005; endyear=2009; flag=0; output; startyear=2006; endyear=2009; flag=1; output; run; data want; set have; if flag=1 then endyear=2020; run;
01-13-2016 05:12 AM
Thanks for your reply, but I think the operation I try to perform should be no problem. Especially since this is the easiest and simplest one I tried recently (when formatting, altering and reducing the 2GB file everything worked fine, so I don't believe a 100MB file with a single operation should cause any problem).
01-13-2016 06:15 AM
As I said, SQL can be quite resource hungry. You can also try clearing out work folders, if you right click on work in Explorer window in SAS, you can see the path to the work directory. Go there and clear out the files. Also right click on that folder and check how much space there is.
03-11-2017 04:34 PM
I´m having exactly the same problem. I used to access SAS with VMWARE, after a couple of weeks, it didnt work anymore. Then I moved to Virtual box. Excelent. Now, after two weeks, the LOG keeps saying:
03-11-2017 04:39 PM
03-11-2017 05:15 PM
But how can this be possible? I ran the same code again and again, always on work are and with success, so it overwrited the tables, not increasing table size.
Im now uninstalling everything to see what happens.
Thank you very much.
03-13-2017 05:29 AM
Please do not necro threads - that means draggin back threads from quite some time and replying with new questions. Every time you do this people who responded originally start getting notifications for threads long since closed. Open a new topic.
03-13-2017 10:42 AM
Best to hit the like button on posts that help, and start a new thread for questions - things might have changed scince that post for instance.