Category: SAS

Example 9.32: Multiple testing simulation

In examples 9.30 and 9.31 we explored corrections for multiple testing and then extracting p-values adjusted by the Benjamini and Hochberg (or FDR) procedure. In this post we’ll develop a simulation to explore the impact of “strong” and “weak” control…

SAS Talks features support.sas.com usage tips

~ Contributed by Melissa Perez, Marketing Specialist, SAS ~ As most SAS customers are well aware, there is a load of content on support.sas.com. But how do you know where to find that information? Alas, we created a demo to walk through the main sectio…

Web Report Studio: Adding Drill-Down Filter Based on a Date

When I was creating the Summary and Detailed reports for the SAS Global Forum paper, I was demonstrating how to link from the weekly chart to the detailed report about the week.  On my first try with my Week Filter based on the date value – it just would not work.  Eeek!  To fix the problem I made a new data item that was a character value.  This posts talks about my strategy.  [You can read our paper “Get Your Fast Pass to Building Business Intelligence with SAS and Google Analytics”.  The presentation goes into more detail, but here’s some past articles about Google Analytics. ] What Should Happen When you click on the bar that represents the week – you actually drill-down to the Weekly Detailed report. You cannot use a date value as this filter – you must use a character based filter for this prompt.  If you need help setting up the filter or creating the link – just refer to the  ”Get Your Fast Pass to Building Business Intelligence with SAS and Google Analytics” paper. Creating the Proper Filter in the Information Map First you need to create a data item based on the date variable.  I used a CASE statement to test if the week was […]

my 5 Important reasons to use Proc SQL

• Proc SQL requires few lines of SAS code compared with datastep and or Proc steps
• Frequency counting can be done in no time… which is very helpful during the QC or validation
• Proc SQL can merge datasets …

Using PROC SQL to get the schema of a MySQL database

It’s Friday, and on SAS Voices they are posting fun stuff about dogs who work at SAS. I’m posting about PROC SQL and MySQL. You tell me – which of us knows how to ring in the weekend with style? I’ve been working with MySQL data sources lately, and SAS/ACCESS […]

Use the set operator UNION in PROC SQL

SQL syntax contains a few set operators, such as UNION, EXCEPT and INTERSECT. The UNION operator concatenates the results of multiple SQL queries vertically into a single table for all matching rows, which I found particularly useful in PROC SQL while…

SAS BI: Does Your Organization Have a BI Strategy?

One of the best things about attending the SAS Global Forum is all the brilliant people you get to meet.  Guy Garrett’s presentation about planning a BI strategy was quiet popular and I have to say he was very witty.  Turns out implementing a BI strategy is similar to dating – who knew?  Anyway – here’s a follow up from Guy – I encourage you to sign-up for the Achieve Intelligence monthly newsletter for more goodies. What is Your BI Strategy?  I recently had the pleasure of presenting a paper on “How to Create a Business Intelligence Strategy” at the SAS Global Forum in Orlando. I started off by asking for a show of hands if the organisation the audience worked at had a current existing BI strategy. Out of approx 150 people only 20% put up their hands. I then followed this up with a further question: “Keep your hands up if your BI strategy is documented and accessible so that all information consumers at the organisation know what the strategy is.” Three hands remained.  Check the Roadmap! Anyone who has kids knows the heart crunching moment when you’ve just started on a long journey and they say “Are we there yet?”. […]

SAS Stored Processes: 3 Tips to Improve Your Prompts

SAS stored processes are similar to SAS programs in that they use the same programming language.  Many of my SAS programs I created early on were only used by me, so I could live with  a little uncertainty and it was easy enough to check the logs for any issues.  If anything went wrong then I knew what I had to change. Stored processes required a whole new level of thinking – my first few stored processes back in the SAS 9.1.3 days were – well they left a lot to be desired.  When I would roll out a new stored process I would often get a call from a user who had done something crazy and the stored process wouldn’t work.  For instance, why would anyone put a state name in a customer name field to see if it would return all the customers from that state?  Only one thing could happen – no report!   Here’s some usability tricks that I have learned with my SAS Stored Processes to make them more robust and harder to break.  Really the out-of-the box prompts provide a lot of functionality that really helps. That’s right – let’s build a better mousetrap! Tip #1: […]