Whether the datasets in library cost the CPU, and where they are stored physically?

[Phil_NZ]

Hi SAS Users,

The interface Serve is very useful for me because apart from it can link me to all the SAS datasets in my computer, but I can also see all datasets inside all the libraries. Super convenient!!

I just wondering, if SAS EG stores a lot of datasets like that, whether it costs the RAM or else?. And what is the directory for these datasets (I mean physically access).

Warmest regards.

[ballardw · Accepted solution]

This will show where all your libraries are physically located:

 proc sql;
    select distinct libname, path
    from dictionary.libnames
    ;
quit;

(or open the view sashelp.vlibnam)

No clue what overhead may be in the EG metadata management because of the connection to server. The server maintains the actual metadata and provides it when needed.

[Phil_NZ]

Thank you @ballardw 

Very useful code, I can see the bigger picture now. Thank you for broadening my horizon.

Warmest regards.

[mkeintz]

A possibly useful tip.   Because I work in an environment with many libraries, sorted alphabetically, often WORK appears below the bottom of the LIBRASRIES list.    I avoid scrolling by providing an alias libname for WORK:

libname _w (work);

which sorts at the top.

[Phil_NZ]

Hi @mkeintz 

It is a very nice and hands on suggestion, I will apply for sure.

However, can I ask how to apply it globally in my SAS EG

I type the code given

libname _w (work);

then execute it, however, there is nothing change from the Serves interface.

Could you please hint me about this issue?

Warm regards.

[mkeintz]

---

@Phil_NZ wrote:

Hi @mkeintz 

It is a very nice and hands on suggestion, I will apply for sure.

However, can I ask how to apply it globally in my SAS EG

I type the code given

libname _w (work);

then execute it, however, there is nothing change from the Serves interface.

Could you please hint me about this issue?

Warm regards.

---

After executing the statement, click on "libraries", then on the "refresh" icon.  

You can make this automatic by putting the statement in an autoexec.sas file.   See Autoexecs - the SAS Enterprise Guide advantage. I would choose the option under "Setting up a user-specific autoexec".  

[Phil_NZ]

Hi @ballardw 

Can I ask why do you use the "distinct" in the code given?

Normally, when dealing with the dictionary, I just see people use select column names, it is the first time I see the use of distinct here. Could you please explain why you use distinct here?

Warm regards.

[ballardw]

---

@Phil_NZ wrote:

Hi @ballardw 

Can I ask why do you use the "distinct" in the code given?

Normally, when dealing with the dictionary, I just see people use select column names, it is the first time I see the use of distinct here. Could you please explain why you use distinct here?

Warm regards

---

Learning point: Run it without distinct and see what you get.

The libname path are repeated in that particular view because of multiple values for the Sysname and Sysvalue variables which you might include to find out stuff like the Filename (in the case of libraries that point to files such as XLSX), Owner Name, or File size which has two options for reporting K or bytes. If you added one of these variables you wouldn't need distinct to only have one libname path combination.

[SASKiwi]

Please bear in mind that Enterprise Guide is merely a user interface. It is not the software processing your data. In your case you have a local SAS server running on your PC doing all the work and EG is just managing that and showing results. Open Windows Task Manager (right click on Windows Task Bar and select) and you will see separately EG and the SAS server both using different amounts of memory and CPU. 

[Kurt_Bremser]

Right-click on Libraries, then Refresh.