In SAS Viya 4 you can create Reports in SAS Visual Analytics that you may want to move around between machines. What if you want copy a report for example from a development environment folder to a production environment folder? You may want to work on the report in one system before putting it onto a final system and making it generally available. Or you may want to have a backup copy saved for recovery purposes. This blog post provides an updated description of how to easily save off SAS Visual Analytics report content to a file and easily move it between machines.
Tag: SAS Environment Manager
Newcomers to SAS Viya Administration may appreciate these tried-and-tested patterns for securing folders, and the content within them (reports, data plans, models etc.). If you are new to security model design in SAS Viya, this post is for you.
In SAS Viya 3.4, promotion support has been added for many additional SAS 9.4 resources, making it easier to make the leap to Viya. In this blog, SAS' Gerry Nelson reviews this new functionality.
In SAS Viya 3.2, the Self-Service Import provides a mechanism for a user to import (copy) data into the SAS Cloud Analytic Services (CAS) environment. The data is copied as a .sashdat file into the selected CAS Library location when it is imported. Self-Service Import data can only be imported into
The report-ready SAS Environment Manager Data Mart has been an invaluable addition to SAS 9.4 for SAS administrators. The data mart tables are created and maintained by the SAS Environment Manager Service Architecture Framework and provide a source of data for out-of-the box reports as well as custom reports that any
One very useful type of auditing for a SAS administrator is to have summary data about the availability and performance of various resources (platforms, servers, services) from the 30,000-foot view. Using SAS Environment Manager, it's easy to go in and look at the availability of any one resource over various time spans--for
Ciao a tutti e ben ri-sintonizzati sulle frequenze di Radio SAS Technical Support per le prime 5 posizioni della classifica delle domande più frequenti da parte dei SAS Administrator al Supporto Tecnico SAS! La volta scorsa abbiamo visto queste posizioni dalla 10 alla 6: 10. COME CONTATTO IL SUPPORTO CLIENTI SAS?
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,
As an addendum to my previous two blogs on using the SAS Environment Manager Report Center, this blog illustrates further tips and tricks you can use to help make the creation of your custom reports easier. The Ad-Hoc Reporting section of the Report Center is specifically designed to provide a
My previous blog discussed the SAS Environment Manager Report Center, and talked about its organization, and how to start using some of the prompts to get the reports you want. The next step is to learn to use some of the example reports provided to help you design your own, production-level
The SAS Environment Manager Report Center is a set of SAS stored processes and SAS macros which leverage the SAS Data Mart for the purpose of monitoring and auditing a SAS installation. Full documentation on the structure and functioning of the Data Mart can be found in the SAS Environment Manager
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
We all know that alerting is one of the most powerful features of SAS Environment Manager; the flexibility and comprehensiveness of this feature is one of the things that makes SAS EV stand out among monitoring tools. If we dig a little deeper, we find that we have quite a bit of
In my last blog, I demonstrated how to configure a SAS server to write a record to a log file showing who is opening, editing or renaming a SAS table. In this blog we will see how we can process that information. The documentation shows one way to do this via
Many administrators are familiar with the well-known “WIP Data Server” component of a SAS installation–so this blog takes a closer look at it, and shows how easy it is to monitor how large the database is growing. This data server contains a SAS-critical database known as the SharedServices Database, which is
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
In a SAS Environment there is a lot of metadata, metadata about configuration such as server definitions, users, groups and roles and metadata about content like data, reports and jobs etc. SAS Administrators often want to report on metadata. They want to know what reports have been developed and where they are stored, what
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
An important goal of SAS Environment Manager is to communicate with existing software systems. This capability includes not only monitoring other non-SAS platform resources, but also means having the ability to respond to events from outside the SAS platform. We’ve seen how SAS Environment Manager can generate an event for external consumption (see Scott McCauley’s
Many larger SAS deployments have multiple instances of similar SAS-related servers. For example, a distributed SAS Enterprise BI environment may have several machines running instances of the object spawner or the OLAP server. Similarly, all of your distributed SAS Visual Analytics deployments have worker nodes that are typically dedicated Linux
As SAS administrators, I know you are as excited as I am by the ability of SAS Environment Manager to monitor, in detail, the performance of their SAS environments. Now, we have a robust tool to monitor, measure and report on the performance of the various SAS components. An added
Several new capabilities and components are available in SAS Environment Manager 2.4, the web-based administration solution for a SAS environment. For me, the most important enhancement is probably the SAS Environment Manager Service Management Architecture Framework, which provides features and functions that enable SAS Environment Manager to fit into a
While previous SAS releases provided high availability through custom-designed failover techniques, many customers requested more robust failover or cluster support for high availability. The SAS 9.4 Metadata Server cluster was introduced to help address this need. A SAS Metadata Server cluster is a coordinated set of metadata servers that act
If you’ve used SAS Environment Manager, you know what kind of information it’s capable of providing – the metrics that show you how the resources in your SAS environment are performing. But what if it could do more? What if it could automatically collect and standardize metric data from SAS
SAS Environment Manager 2.1 (which was released with SAS 9.4 M1), has new features to make it easier to manage your SAS environment. For example, it now supports metadata clusters, and it has an improved method for handling access to the application. But the biggest change is in metadata access.