Starting with SAS 9.4, not only will SAS administrators see lots of processes running on your operating system supporting the various SAS servers (such as SAS Metadata server), you will also see two new processes that have a description of “agent” running. Agents are software processes responsible for tasks such
Software performance is a complex topic. The answer to every question depends—depends on hardware, depends on operating system, architecture, time of day, number of users and so on. (Margaret Crevar gave us some insight into that complexity in her January 2013 post Improving performance: Understand the problem.) That’s why we
Over the past few releases, SAS has offered high availability for servers through various failover techniques. So I’ve been wondering how metadata clustering differs and why does SAS 9.4 provide it. The “why” is an easy question to answer. Today’s SAS software is used in a wide array of business-critical applications
In my last post, I introduced the hardware solutions (such as a virtual IP switch or IP load balancer) that enable client applications to access services regardless of whether they are running on a primary or a failover server in a grid-enabled environment configured with high availability. In this post,
Like most SAS users and administrators, you usually don't know where your backend SAS servers are located--probably in some basement server farm or perhaps another building or even another town. But I'm sure you do know that your SAS client application must have a way to reach services running on
