Read Access Violations or Segmentation Violations might occur in PROC SQL when you make a calculated reference to a nonexistent column.

The problem occurs when the SELECT statement selects more than 16 columns and the expression containing the calculated reference is the last expression before the FROM clause. This situation prevents the actual error message(s) from being written to the SAS log, which should be as follows:

 ERROR: The following columns were not found as CALCULATED references in the immediate query: column_name.

Click the Full Code tab to see an example that generates a Read Access Violation.

A fix for this issue is planned for a future software release.

Operating System and Release Information

data one;                                            
 retain v1-v16 0;                                    
run;                                                 
                                                     
proc sql;                                            
 select                                              
   v1                                                
  ,v2                                                
  ,v3                                                
  ,v4                                                
  ,v5                                                
  ,v6                                                
  ,v7                                                
  ,v8                                                
  ,v9                                                
  ,v10                                               
  ,v11                                               
  ,v12                                               
  ,v13                                               
  ,v14                                               
  ,v15                                               
  ,v16 as new_v16                                    
       , coalesce(1, calculated new_v16) as New_V17  
 from one;                                           
quit;