Skip to main content

Metadata Objects - where are their physical files stored?

As a new user to SAS I always wonder what is metadata. Immediate answer that cross my mind is data about data. In SAS, metadata is a pointer to an external content. Okay, then where is the content? Where they are stored? This article focus about all the metadata objects in SAS and their physical location.
Note: Physical refers to the location (computer or server) where file is stored.

Metadata Objects in SAS

I have seen many SAS admins work with metadata objects, still they didn't learn that they are working with metadata object. If you are one such user below is the list of SAS Metadata Objects in SAS.

Metadata Objects and their physical location

Folder object

It is used to organize data in hierarchy. It doesn't have physical location. It is a virtual view data organized in hierarchy.

Library object

Library object holds the connection information and physical library location. It also have the libref or nickname of the library. Physically it is collection of tables, generally a folder or directory stored in the OS or RDBMS.

Table object

It holds description of the table like what column it has, index information and library where the table is stored. Physically it is table maybe SAS data sets. You might have seen some files with extension sasbdat in SAS host server, they are the tables stored physically.

OLAP cube object

It contains information about description of cube such as dimension, level, measure, drill through table and schema. In physical, OLAP cube will be is a hierarchy of multidimensional data. They are ysed for quick analysis.

Information map object

It holds collection of data items and filters. Inf
o map are used to provide user friendly view of data and don't have physical location. They actually points to table and cubes.

Stored process metadata

It holds the location of SAS code. It can also have other information like server used for execution and the type of output it will create. SAS code will be stored in server.

Report metadata object

Holds location of report and the associated files. Files are usually graphical content will be stored in SAS Content Server.

Server Metadata Object

Contains information about host machine where the server is created. Port details will also be available. In physical location it will be configuration file and log of the server.

User Metadata Object


Will have user id and other user related information such as name, email, display name etc. Physically they are stored as user name and password in authentication provider database.

Group Metadata Object

It is a set of user metadata object. There is no physical location for group metadata object. However you are allowed to associate an external account with a group. 

Comments

Post a Comment

Popular posts from this blog

Insufficient authorization to access PIPE error in SAS EG

Issue: When I tried to run SAS code in SAS Enterprise Guide it throws following errors: ERROR: Insufficient authorization to access PIPE. ERROR: Error in the FILENAME statement. Screenshot of error: Solution: This error occurs when you try to run OS commands in SAS code. To run the OS commands in SAS code you need to enable XCMD option. You check it in SAS Management Console by following below steps.   Open SMC -> Expand Servers -> Expand   In SASApp , expand Logical Workspace Server -> right click on Workspace Server. Click properties -> option tab -> advanced options -> launch properties. Check whether Allow XCMD is checked. The issue arises if the Allow XCMD is not checked. In above image, Allow XCMD option is not checked. It should be checked to run OS commands from SAS code. In Unix /Linux machines, this XCMD option can be enabled by using system option XCMD in sasv9 config file or workspaceserver.sh script f...
2 comments
Read more

The authentication server is not SETUID ROOT error in SAS

Question: When validating the SAS Server from SAS Management Console, I received the following error: The authentication server is not SETUID ROOT.  So, I ran the setuid.sh utility and restarted the services many times. I just checked the elssrv sasauth sasperm setuid bit. There were no error in sasauth-debug.log, sasauth-access.log, sasauth-error.log.  Any suggestions? Answer: Please do the following:    1) Run /<SASConfig>/Lev<X>/ObjectSpawner/ObjectSpawner.sh stop  2) Edit /<SASConfig>/Lev<X>/ObjectSpawner/ObjectSpawner.sh and add the code shown below right after SCRIPT=`basename $0`:  if [ -n ""$TKPATH"" ]; then  unset TKPATH  fi   if [ -n ""$TK_PATHLIST"" ]; then  unset TK_PATHLIST  fi    3) Run /<SASConfig>/Lev<X>/ObjectSpawner/ObjectSpawner.sh start  The above code change in ObjectSpawner.sh should fix the issue.
1 comment
Read more

SAS - CLI error trying to establish connection

Issue: User asked me to make a database connectivity to SQL Server. They provided following details SQL server hostname and ip address Database/DSN name Username Password I made entry in ODBC.ini file. You know, SQL Server entries were made in ODBC.ini and Oracle entries were made in TNS.ora file. Everything went fine, took back up of odbc.ini, made entry and saved the file. So to test this connection I ran the libname statement in SAS Enterprise Guide 6.1. It throwed following error. Error Message: My DB team showed that they are able to login   14 GOPTIONS ACCESSIBLE; 15 LIBNAME test ODBC DATASRC=SGE_DS SCHEMA=VST USER=sales PASSWORD=XXXXXXXXX; ERROR: CLI error trying to establish connection: [SAS/ACCESS to SQL Server][ODBC SQL Server Legacy Driver][SQL Server]Login failed for user 'sales'. Solution: First I suspected that Login failed for user 'sales' meant the password provided by DB team was wrong. They responded that they were able to login wi...
3 comments
Read more