Hi @sastpw , a quick question. In the example that you share, is it necessary the "**" before the name o "oda" variable?     Regards,  ... View more

Thanks! ... View more

Hi @gwootton ,   I'm creating the test tables on WORK area. In one of my test, I created the tables first. Then opens it and navigate on each of them and everything were fine. After that test, closes the tables and I ran the JOIN process and the erro appears.    Follows the program used for the test (it's very simple). If I run the program with 5 character columns and 130 numeric columns, it executes fine. But if I increase to 140 numeric columns the error appears.    %LET COL=5 ; %LET COL_N = 135; DATA VALIDA; ARRAY VAR_(&COL_N); ARRAY STR_(&COL) $50.; DO j=1 TO 30000000; DO I=1 TO &COL_N; VAR_(i) = RANUNI(0); END; DO I=1 TO &COL; DO n=1 TO 40; SUBSTR(STR_(i), n) = BYTE(INT(65 + 26 * RANUNI(0))) ; END; END; OUTPUT; END; RUN; DATA VALIDA2; ARRAY VARI_(&COL_N); ARRAY STRI_(&COL) $50.; DO j=1 TO 30000000; DO I=1 TO &COL_N; VARI_(i) = RANUNI(0); END; DO I=1 TO &COL; DO n=1 TO 40; SUBSTR(STRI_(i), n) = BYTE(INT(65 + 26 * RANUNI(0))) ; END; END; OUTPUT; END; RUN; PROC SQL; CREATE TABLE VALIDA3 AS SELECT a.*, b.VARI_1, b.VARI_5 FROM VALIDA a LEFT JOIN VALIDA2 B ON a.VAR_1 = b.VARI_2; QUIT; Regards.  ... View more

Thanks @gwootton. Both tables are SAS and it created in previous steps. As test, we created 2 new big tables (totally random) and the same erro appears.    We also tested create a big file, directly on the filesystem (without SAS) to see if any erro appears after reach some size, but the file was created without any erro.    We also reviewed the block size for both environment and it has the same definition.    ... View more

Thanks @SASKiwi . I'll share the notes with server admin, tomorrow morning, and let you know. As far as I know, there is no limit (quotas) per user, but we'll check it again.    Regards,  ... View more

Thanks @Kurt_Bremser . In fact, we made test with and without compress options. Because we are in testing phase, we have a lot of WORK area available, almost 11TB free. We monitored the free WORK space during executing and it never pass over 11% of usage.    We already have a ticket opened with SAS Support but, after more than 1 week we don't have any update on it.  ... View more

Thanks @ballardw . Yes, we know PROC SORT or SQL JOIN without index use a lot of disk space. But the weird situation is these particularly process, created by an enduser, runs ok on our environment with 9.4M5. It's a simple LEFT JOIN between 2 SAS tables. The first one is big, not the second one. The join is for 2 columns.    ... View more

Thanks @SASKiwi . How could I check the user space quotas? We didn't define any specific user quotas. In fact the process stop when rich almost 600GB of WORK space used. ... View more