One of the jobs of SAS Administrators is keeping the SAS license current. In the past, all you needed to do was update the license for Foundation SAS and you were done. This task can be performed by selecting the Renew SAS Software option in the SAS Deployment Manager. More recently,
Tag: configuration
In a couple of my previous blogs I discussed how to audit who made changes to data in a SAS environment. In the last couple of weeks I have been asked how to do the same thing for SAS Visual Analytics reports and explorations. The Visual Analytics administrator overview report
Everyone who codes with SAS knows what the SASWORK directory space is, and everyone who has ever managed a medium-large installation knows that you need to monitor this space to avoid a huge buildup of worthless disk usage. One of the most common snarls happens when large SAS jobs go
SAS 9.4 M3 released in July 2015 with some interesting new features and functionality for platform SAS administrators. In this blog I will review at a very high level the major new features. For details you can see the SAS 9.4 System Administration guide. SAS 9.4 M3 includes a new release
One of the great things that the new Data Mart will do for you is combine data from all the machines found in a multi-machine deployment into one storage area, where it is used to create many of the reports found in the Report Center. This capability began with the 14w41
SAS recently performed testing using the Intel Cloud Edition for Lustre* Software - Global Support (HVM) available on AWS marketplace to determine how well a standard workload mix using SAS Grid Manager performs on AWS. Our testing demonstrates that with the right design choices you can run demanding compute and
SAS System software supports a wide variety architecture and deployment possibilities. It’s wild when you think about it because you can scale the analytic power of SAS from the humblest single CPU laptop machine all the way up to hundreds-of-machines clusters. When SAS deployments involve many machines, it’s natural to
In previous posts, we’ve shared the importance of understanding the fundamentals of Kerberos authentication and how we can simplify processes by placing SAS and Hadoop in the same realm. For SAS applications to interact with a secure Hadoop environment, we must address the third key practice: Ensure Kerberos prerequisites are met
When SAS is used for analysis on large volumes of data (in the gigabytes), SAS reads and writes the data using large block sequential IO. To gain the optimal performance from the hardware when doing these IOs, we strongly suggest that you review the information below to ensure that the
"Do I really need a detailed technical architecture before I start my SAS Deployment?" My team gets asked these questions all the time: Do we really need to spend the time for the above exercise? Why can’t we just start doing the deployment of SAS and fix issues if they come