From an Enterprise Guide user's perspective, a SAS library is a library. Whether it was defined in the autoexec or in the metadata or by magic, it is there for them to use with no issues. However, there is a difference as metadata defined libraries do not behave in the
Author
SAS Technical Support has a wonderful how-to guide for using one set of prompt values across multiple sections of a Web Report Studio report. This works great in 4.2, however there is one additional item that I discovered in a 4.3/9.3 install. With the addition of PROC STP and SAS
Each spring and fall, I start clearing out the kid's small clothes, old toys, etc. It can sometimes go too far and reach into my "digital pack-rat" issues. (Wait, what does that mean? Well, just ask the person who last week requested detail on a project I worked 3 years
BASE SAS users are already familiar with the autoexec file. This is a .sas file that typically resides in the installation folder of the SAS executable. Instructions for setting it up in UNIX, Windows, and other environments is readily available on the SAS website. In SAS BI configurations there are
Last week I provided the steps for how to go on a date, at least by using dynamic prompts in BI Dashboard. Now that you have seen how to create them, lets discuss making them smarter. For this example, the customer is asking for two prompts to affect a single
Who says anyone is an expert at something? I definitely do not when it comes to SAS (well, anything for that matter). Each time I sit through a presentation at a conference I learn something new. During the SAS Western Users Conference, fondly know as WUSS, this month I learned
Wizard Harry Potter makes magic just waving his wand around and shouting out spells. Using SAS Enterprise Guide (and you are welcome to shout out your own commands too) you can create some magic, allowing the Stored Process Wizard to code for you. On Step 2, the "Include code for"
A common question really and one that I get after posting code like yesterday's All SAS Stored Process Locations Report. The neat trick is just to type METABROWSE in a BASE SAS command window. (There are two other commands: METACON and METAFIND. Has anyone got any tips on when those
Stored process code can exist within the metadata itself for version 9.3 (the benefits of which I discussed earlier). But for all other versions (and as a option in version 9.3) the SAS code is stored as a .sas file within the server's file system (or mapped folder/drive structure). When editing
The date prompt from SAS Prompt Framework provides the options of single selection or a range, however what if you need to select multiple individual dates such as Monday (May 28), Wednesday (May 30), and Friday (June 1) of last week? There are a few alternatives to accomplishing this. Option
Did you change your LinkedIn password yesterday? (If you didn’t, you should!) But did it happen to be the same as your corporate password? First, tisk tisk. Second, change your corporate password NOW! Ok, now that this is done ~ don’t let your saved connection profile for SAS applications lock
What if you would like to make a copy of an existing stored process to test out your changes before making them live? The copy command is available from within SAS Management Console or from the SAS Enterprise Guide Open Stored Process GUI as seen below (note you can only
This past Monday, Tricia and I released our 2nd book this year. "The 50 Keys to Learning SAS Stored Processes" provides a step-by-step approach to transitioning from SAS code into user driven (prompted) stored processes. Trimming down all the things you can do with SAS Stored Processes is next to
PROC STP is a new procedure for SAS 9.3 Stored Processes. It's so new and different that I have not had the opportunity to use it yet in a customer engagement. When writing about it for the now released "The 50 Keys to Learning SAS Stored Processes" book, I had
When you are constantly taking the data tables and completing joins to begin working on your reports or analysis it might be time to consider creating permanent views. Then you can just add the view to the Enterprise Guide project rather than dealing with the joins in a Query Builder
After unwittingly getting involved recently in a code vs GUI discussion another pro GUI vote came in yesterday when presenting to a customer's internal user group. When creating and using prompts in SAS Enterprise Guide, it is a no-brainer to recommend leveraging the %_eg_WhereParam as it handles all the special
During IFSUG yesterday, Sunil Gupta gave attendees to his presentation a special homework assignment. Look into the SAS Enterprise Guide task 'Characterize Data'. Sunil suggested that this was a simple approach to quickly getting a summary of all the variables within your data table. Of course, some programmers will use
Today at IFSUG, Chuck Patridge presented a wonderful talk about how to complete fuzzy matching using BASE SAS tools. Chuck has been programming SAS since 1979 and has been tasked multiple times with coming up with in-house solutions to address business needs without the software costs that are typically associated
Unlike BASE SAS tables, OLAP cubes must exist in within the metadata in order to access from any of the OLAP Viewers. In addition to having some metadata OLAP cubes have a physical file structure presence (at least for MOLAP/HOLAP because it's a different story for ROLAP). When you refresh
Unlike prior versions of SAS OLAP technology, 9.2 provides more options for maintaining and refreshing OLAP cubes. With this comes some discussion about what each one does alone, and how pairing these techniques really provides SAS OLAP Server Administrators and cube developers a cornucopia of OLAP options. PROC OLAPOPERATE Remember
In one minute (and 10 seconds, but are you measuring that?) you can add a custom measure (also known as calculated members) to your OLAP cube. Watch this video to create a simple calculation multiplying units * price. Remember that this mechanism is not just used for multiplications, you can
Drill-through to detail is the ability to right click within a cell of a web report or OLAP viewer and request the detail source records that make up that specific cell's measure. The maximum number of records, by default, is set to 300,000. Feasibly the report user could download all
Years ago and a seemingly far galaxy away, I wrote about how to modify 9.1.3 to start Enterprise Guide users in a different location for the File folder. By default, the user only can access their personal SAS Temporary File. Why change this? I would prefer to use a central
Functionality to upload files onto the SAS server (from 9.2 on) is available using stored processes and an html input type="file". I introduced this topic last year in my blog post using the SAS Stored Process Developer Guide sample. Of course, it is never as easy as the sample is
When trying to write out graphics to a specific filename location, the gsfname option is only honored when ODS LISTING is turned on and ODS HTML is turned off. This is especially important in 9.3 Base SAS as the ODS HTML option is the default output destination. Enterprise Guide users
Just got some time to begin playing with the 9.3 Enterprise Business Intelligence installation on my SAS laptop. As I was testing out the web applications, SASWebDoc opened but I couldn't get to the SAS login screen up to access the SAS Stored Process web application. First I started perusing my
Creating shared prompts to use across the various BI clients requires the use of SAS Management Console's stored process wizard. Editing these prompts after they have been shared requires some forethought. The important thing to consider when making any changes to a prompt's properties is the impact these changes could
In order to support a SAS Server Architecture, administrators must know where all the log files from the various SAS Business Intelligence services are located. By default, each service that generates a log will create it within the services' own configuration folder structure. For example, the metadata server log is
SAS procedure SUMMARY is a quick method of converting your detail table to a fully summarized one. Included is a sample. The key option to set is the NWAY - this generates the lowest level of summary for use in the OLAP cube. Essentially - the class statement contains all
SAS allows for three different cube storage mechanisms: 1. MOLAP The traditional SAS OLAP Cube will all aggregations / nway stored on a physical file structure accessible by the SAS OLAP Cube Server. 2. ROLAP A relational OLAP cube - where no aggregations are stored and SAS points to the