SAS Viya is an exciting addition to the SAS Platform, allowing you to conduct analysis faster than ever before and providing you the flexibility to utilize open source technologies and generate insights from data in any computing environment. The blog post “Top 12 Advantages of SAS Viya” does a great
Last week I described how to use PROC IOMOPERATE to list the active SAS sessions that have been spawned in your SAS environment. I promised that I would share a custom task that simplifies the technique. Today I'm sharing that task with you. How to get the SAS Spawned Processes
If you're a SAS administrator, you probably know that you can use SAS Management Console to view active SAS processes. These are the SAS sessions that have been spawned by clients such as SAS Enterprise Guide or SAS Add-In for Microsoft Office, or those running SAS stored processes. But did
SAS administrators now have another tool to keep SAS users from straying off their permitted path: the LOCKDOWN system option. The option was introduced in "stealth mode" for SAS 9.4. In SAS 9.4M1, it became a true, documented option. For the official guide to creating "locked-down servers", see the SAS
My children learned this skill early in life: when you want to secure permission for a questionable activity (say, "watch 5 hours of Phineas and Ferb" or "eat a bowl of candy for breakfast"), you should approach the most lenient adult in the household. In my early days of fatherhood,
When I work on SAS projects that create lots of files as results, it's often a requirement that those files be organized in a certain folder structure. The exact structure depends on the project, but here's an example: /results |__ html |__ images |__ xls |__ data Before you can
In a previous post, I described how to write a Windows PowerShell script to connect to a SAS Metadata Server. In this post, I'll show an example of something useful that you can do after you've established that connection. Specifically, I'll show how to "ask" the SAS Metadata Server about
SAS Integration Technologies provides a flexible platform to create all types of apps, from simple utilities to full-blown applications. As part of the research for my SAS Global Forum 2013 paper (Create Your Own Client Apps Using SAS Integration Technologies), I've been trying to invent some useful examples that you
I've bragged about how easy it is to install custom tasks for SAS Enterprise Guide. It's simple: you copy the .NET assembly (usually a single DLL file) into one of the designated folders in your SAS Enterprise Guide installation, and your task just shows up in the menu. Since I
As I mentioned in my introductory post about Windows PowerShell, you can use PowerShell commands as a simple and concise method to collect data from your Windows systems -- information that is ripe for analysis within SAS. In this example, I'll show a technique for using a SAS program to
Windows PowerShell is one of my favorite tools to use for gathering information from my PC and network, and also for automating processes. If you are familiar with UNIX shells (such as Korn shell or its variants), you will probably be very comfortable with Windows PowerShell. Just like its UNIX
Many people mistakenly assume that just because you want to use a SAS program to access a protected resource (such as a database table), you must include the credentials for the resource inside your program. Few things cause a database administrator to lose more sleep than coming across this within
It was over two years ago that I shared the tip of using Process Explorer to look under the covers at which SAS processes were running on your Windows environment. Process Explorer recently received a refresh, and it's worth downloading the new version. (Yes, it's free.) If you want to
Like any good SAS professional, I subscribe to the SAS Samples RSS feed. The other day I found this sample that shows how to create a PDF report about the contents of a SAS Information Map. It's a nice example: it shows how to use the INFOMAPS engine and ODS
If you deploy the SAS 9 environment on Windows, you may have multiple SAS processes running on a single box (metadata process, OLAP server, multiple workspace servers). Windows Task Manager doesn't provide a great way to distinguish one sas.exe process from another, but Process Explorer does. Process Explorer lets you
