As I understand it, you can set authorizations to libraries inside SAS Viya. But, this probably won't stop user from accessing the library path directly. "The data source definitions do not reside in folders and are created with READ permissions for all authenticated users. Operating system permissions to the library physical paths are respected by the Compute server when the libref is assigned. This means that if a user cannot read the file-system directory they will not see the library in their SAS session." https://communities.sas.com/t5/SAS-Communities-Library/Managing-Connections-to-Data-Sources-and-SAS-Libraries-for/ta-p/825138 ... View more

Base libraries uses file system authorizations, so speak to your platform/security team for guidance. ... View more

I don't think there's any reports OOTB for SAS Management Console. SAS Content Assessment has som reports on usage and products. If you have Viya 3.5 you can view them in VA. Otherwise you can probably build your own reports from the data mart tables that is generated. ... View more

I suggest that post screen shots as images, many here is a little weary of opening more complex file formats (that can bear unwanted embedded malware). But I'm a bit confused. First you are discussing  meta nad compute, and assume this is 9.4. But your next post is about Viya? If these are to separate issues, have them in to seperate threads. ... View more

It's kinda hard to see what you really want to achieve. Please attach sample input data and desired output. ... View more

If the tables are already sorted by Custid, use @Kurt_Bremsers suggestion. Otherwise SQL FULL JOIN is a simple query. proc sql; create table want as select coalesce(aa.CustId, bb.Custid) as CustId, coalesce(aa.Y, bb.Y) as Y from aa full join bb on aa.CustId = bb.CustId ; quit; ... View more

Some kind of sort operation is needed, regardless of technique chosen. I would go for the approach of having the data sorted by id (assume facilities within each id is what you are looking for), facility and start date. Then use REATAIN for two new variables to keep your start and and dates across observations. And then an explicit OUTPUT when the gap is greater than 31 days or your reach an new id/facility combination. ... View more

SInce you use the term "Project", does it mean you are in Enterprise Guide? Regardless, I would create a copy of the project, and then delete nodes in each (maybe keep another copy of the original until verified ok). ... View more

"How can I know what is the libaname  code that connect between sas and tera here??? I dont need to run the libaname in order to run it but I think that in background it is running but I dont know what  libname is running ." Do you want to know specifically what Terdata instructions the libname statement triggers? Try this before your libname: options sastrace="d,,,ds" sastraceloc=saslog nostsuffix msglevel=i; If you are interested what SQL is sent down, you can settle for: options sastrace=",,,d" sastraceloc=saslog nostsuffix msglevel=i;   ... View more

Unfortunately SAS SQL does not support window functions. And I can't see how to solve this in ANSI 1992 SQL, at least easily. The data step is probably your best option here. ... View more

What kind of assets are trying to reach, and how do you intend to use them (from SAS)? ... View more

Is your aim to create a smaller permanent data set? Why limit yourself to SQL? If you have SAS/STAT licensed PROC SURVEYSELECT is your go-to for creating samples. If our data set is sorted, you could use a data step to read the first n observations of the specified BY groups. ... View more

The general recommendation when doing updates/appends to a table with indexes, drop the index and recreate after the update/insert operation. I think the reason is that SAS needs to update the index record by record during an update, whereas a create index operation can do a single sort through operation. I think this applies to your scenario as well.   ... View more

I can't find any specific recommendations for ACT:s, more is written about ACE:s. If it's possible you could try to transform your ACT:s and implement ACE:s instead, before migrating? Here' are some starting points: https://documentation.sas.com/doc/en/sasadmincdc/v_067/calcontentmig9x/p0lui94y7l3fz5n1uzg6rgzgdyjy.htm (Section Authorization) https://documentation.sas.com/doc/en/sasadmincdc/v_067/calauthz/p0g0vol9j5o4t0n1381yo6bc6slp.htm   ... View more