SAS Platform Admin Blog

In our organization we had two SAS deployments, one is on premise and another is in AWS. We saw a slow performance of queries against the on premise database. We try to improve the performance by using several SAS options like READBUFF. But still we see there is a significant slower performance when compared to our on premise. In one setup database is in on on-premise and SAS is in AWS, in another set up both SAS and Oracle database is in on premise. The issue reported is with the sas server in the AWS. We saw like for like query performing significantly slower than the on-premises server. Below I am going to explain the process of testing which we took to find out the issue. Testing method I did my testing by running the query from Linux command line using the SQL plus utility. I created csv output using Oracle query and the sas query created the regular SAS dataset. We run query against a table from our on premise database which had 5 million records and 200 plus column. F

Issue: I am successfully able to install SAS CBS (Credit scoring for Banking) and SAS BIS (Banking Intelligence Solution), however configuration fails. Solution: For installing Credit scoring for Banking you must first install and configure DDS (SAS Detail Data Store). Because SAS CSB is dependent on DDS, so install all products except CSB. Then create the physical DDS tables. DDS metadata can be imported using SAS Data Integration Studio or SAS Management Console. Once the above step is done, configure CSB. This time you wont get any errors.

Issue: When I try to run a code to connect to Oracle DB I get message saying sas.exe has stopped working. Full Error Details: ERROR:  An  exception has been encountered. Please contact technical support and provide them with the  following  traceback information: The SAS task name is [OBJECT_EXECUTIVE] Exception occurred at (3F350BF5) Task Traceback Address   Frame     (DBGHELP API Version 4.0  rev 5)   3F350BF5  0351F35C  sasioora:tkvercn1+0xFBB5   62A2FB57  0351F398  sasxdbi:tkvercn1+0xEB17   675611A0  0351F5EC  sasyhl:tkvercn1+0x160   6778D6C2  0351F758  sasyh:tkvercn1+0x2C682   6778C976  0351F8F8  sasyh:tkvercn1+0x2B936 028CB91C  0351FAA8  sasxshel:tkvercn1+0x1A8DC 028B26EA  0351FB34  sasxshel:tkvercn1+0x16AA   028B15E2  0351FB74  sasxshel:tkvercn1+0x5A2 028CF04D  0351FC2C  sasxshel:tkvercn1+0x1E00D   028F5C10  0351FDF0  sasxshel:tkvercn1+0x44BD0 028F990D  0351FE74  sasxshel:tkvercn1+0x488CD 028F3D0F  0351FEAC  sasxshel:tkvercn1+0x42CCF   5861351  0351FF28  sasxobj:t

SAS Information map Studio is used to manage SAS information map. This tool is designed for business users to analyse and build report from data warehouse. The advantage of information map is there is no need to understand data relationship. Business user can just focus on analysis and report. What can I do with information map? With information map you can easily create filter to subset the data in data source. Can connect to the data sources like relational tables are multidimensional olap cube. It actually makes complex data look easy. Role of Workspace server pooling in information map: Workspace server creates set of workspace server processes which are available for certain type of request. They can be reused for subsequent request. The process will be launched by shared identity. By default pooling is done at server side. All the requests are managed by object spawner in case of server side pooling.The object spawner allocates the process by using its load balanc

If you are looking for the steps to migrate your RTDM objects from Test to Prod you can follow the below template. These are the steps which I have followed in-order to migrate the RTDM server from Test to Prod. For migration you need to use SAS Export/Import utility: Export Flow Export Users/Groups Users/Groups exported using the standard SAS Management Console SPK feature Export Folders Folders exported using the standard SAS Management Console SPK feature Export Libraries Libraries exported using the standard SAS Management Console SPK feature Export BRM Rules CSV Export method Export R Models in Model Manager Export throught the PMML Export feature Export Business Context Business Context exported using the standard SAS Management Console SPK feature Export CI Definitions CI Definitions exported using the standard SAS Management Console SPK feature Export RTDM Resources RTDM Resources exported using the standard SAS Management Console SPK feature Export RTDM F

There are chances that metadata service cannot be started due to corrupted metadata repository. Due to this you cannot able to use your new decisions. However RTDM service can work as they have cached version of repository. This makes the system alive and functional for a customer perspective. Will it? We have done testing in our test server unfortunately it doesn't work without Metadata server. Below are the steps we have followed: Stopping RTDM services /software/sas/config/Lev1/sas.servers stop /software/sas/bin/SASFederationServer/4.1/fedserver/bin/dfsadmin stop /software/sas/bin/DataFluxAuthenticationServer/4.1/authserver/bin/dasadmin stop /software/sas/bin/SASDeploymentAgent/9.4/agent.sh stop Midtier: /software/sas/config/Lev1/sas.servers stop /software/sas/bin/SASFederationServerManager/4.1/fsmanager/bin/fsmadmin stop /software/sas/bin/SASDeploymentAgent/9.4/agent.sh stop Metadata and Compute: /software/sas/config/Lev1/sas.servers stop /software/sas/bin/SASF

SAS workspace server Most of our SAS code generated by the application or written by user is executed on a workspace server. It creates a session to execute SAS code for accessing libraries, performing task using SAS language, retrieve results. Types of workspace server  On a broader perspective we have workspace server for admin and non admins. We can introduce server side pooling in SAS workspace server as well. This pooled server will be used by non admin. The workspace server for SAS metadata server is used by administrator. This should be secured for the sas administrators group with metadata permission. How does workspace server works? Standard workspace server create a new process each time a client requests a connection. The process will be owned by the user who is requesting. The connection will be terminated once the user close the session. Desktop user need to close the application to terminate the connection and web user connection will be automatically terminated

In most of the sas platform we have these basic set of SAS servers, they are SAS workspace server SAS stored process server SAS OLAP server SAS batch server SAS/ connect server What you want to know abou these servers? It is important to know the functionality of each server as they have different properties. For any analytics platform all the above server are used. Each of the server uses other SAS utility which should not be confused as the server. SAS object spawner, job scheduler are few examples. Also it is important to know what are the authentication mechanism each server support.  For example, Host authentication  works with Workspace server but it won't work with stored process server. Apart from the server I mentioned above it is most common to see SAS Java batch server, SAS Data step batch server and SAS grid server. On a nutshell these servers are used only during special purposes. I will be explaining about each server in upcoming post.