There is a DATA step solution. (Hmm...maybe there's a DATA step solution to everything.)   Since this requires BY-group processing, start by loading the data into partitions:     libname mycas cas; data mycas.have(partition=(id) orderby=(distance) replace=yes); input id var1 var2 var3 distance; datalines; 1 1 1 1 0.2 1 2 1 2 0.3 2 1 1 3 0.9 2 1 2 1 0.2 3 1 3 2 0.1 ; run;     Then, use the SESSREF= DATA statement argument to insist that the DATA step runs in CAS:   data mycas.want / sessref=casauto; set mycas.have; by id distance; if first.id then output; run; Finally, check the work:     proc print data=mycas.want; run;   There's lots of excellent DATA step in CAS documentation, such as the following: BY-group processing in CAS   (I made an update to this post because I left off the ORDERBY= data set option on the first DATA step.  With the option, the table is already organized according to the BY statement in the second DATA step--avoiding any reorganizing the data to sort it.  Without the data set option, the second DATA step has to make a temporary copy of the table--partitioning and sorting it.) ... View more

If you are OK using PROC CAS and CASL, then check the output of the table.fileInfo action.     proc cas; table.fileInfo / caslib="valasr2"; quit; That should list the tables that are in-memory on your LASR server.  Those are the candidates to transfer into CAS with the table.loadTable action.  This might do it, assuming you find VA_SAMPLE_TELCO03 in the results of the fileInfo action.   proc cas; table.loadTable / file="VA_SAMPLE_TELCO03" caslib="valasr2" /* I assume you want to rename the table to LASR_TEST2... */ casOut={name="lasr_test2" caslib="public"}; run;   ... View more

Row-wise operations can be performed, similar to the ratio example that you showed.   compute sum1 "sum1=sum(mpg_city, mpg_highway)"; compute weird1 "weird1=min(weight, (enginesize * cylinders * horsepower * 2));"; ... View more

The IMSTAT procedure can help with most of what you identify.  I don't know many details of licensing, but check whether you can use the data and server management statements for the IMSTAT procedure, such as the TABLE and UPDATE statements.   For your "Flow with PROC IMSTAT" comments: Your three items are accurate predictions, it should be very fast. I’d also suggest a SAVE statement or some other means to make a copy for reload. For the questions: Q1—there is table-level locking. Requests for data that are already in-flight will see the old data. After the UPDATE request is complete, everyone sees new data. Q2—There will be down time while the in-memory table is dropped and the replacement is loaded.   For the "Flow without PROC IMSTAT", consider reording the steps: 1) Update the “original” data (SAS data set, Oracle, other data source) first. 2) DROPTABLE the in-memory table and then PROC LASR ADD from the updated replacement Users will experience downtime between the DROPTABLE and ADD.   Some of what I wrote assumes a distributed server.  Let me know what I can clarify, and I'm really hoping that you have the IMSTAT procedure and find it useful.   ... View more

That looks like an application issue.  Please contact technical support: Support. Typically, information about authorization grants and denials can be found in the SASLASRAuthorization.log file that is located in SAS-configuration-directory\Levn\Web\Logs\SASServern_m . ... View more

Jaap's response, especially the item in bold, is a very good response. I'll add one more trivially easy way to specify a library as read-only.  There's a Library access field in SAS Management Console that you can use to specify a library as READONLY (that's the menu choice).  See SAS(R) 9.4 Intelligence Platform: Data Administration Guide, Third Edition. A word of caution. As easy as that setting is to configure, if that metadata setting is not also paired by restricting Write access in the operating system, a user can easily circumvent that setting by writing a program with a user-supplied LIBNAME statement to the data. ... View more

For Windows, there's the SAS Drivers for ODBC and the SAS Providers for OLE DB.  I believe that both of those options (certainly ODBC) will require a running instance of SAS to act as a server.  I'd think that's an option if you were considering accessing a database server.  I'm sure there are lots more options. ... View more

In order to read the .sas7bdat files, Base SAS needs to be installed on the machine (so the driver can invoke PROC ODBCSERV) or files must be somewhere that a SAS/SHARE server can access them.  Regarding the local access choice, see the information about the "Startup Parameters" at http://support.sas.com/documentation/cdl/en/odbcdref/63700/HTML/default/viewer.htm#n170ibo0gfz633n1x7xx5pcxqtas.htm ... View more