Best Practices: Letting SAS Enterprise Guide Write MDX Code
SAS Enterprise Guide is a VERY useful client tool for SAS development and data analysis. One the best features is the ability to see the SAS code generated from different tasks. In addition to viewing the Base SAS code used to perform different tasks, you can also view MDX code written to create certain measures, members, and sets in OLAP Cubes.
Adding Simple Measures from SAS Enterprise Guide
Let’s start by creating a simple measure for a Rolling 3 Months of Sales using my SGF2011 cube:
Create a time series measure:
Enter the parameters:
Specify the format:
The next screen summarizes the parameters entered into this wizard. You can see the MDX written here as well. Click ‘Finish’ to define the measure.
You should see the measure in your cube output. Right click anywhere on the grid output to ‘Edit View’ > ‘Edit with MDX Editor’.
This is the output you should see in the MDX Editor:
The measure can then be defined in the cube globally by putting the MDX code in the SAS program which builds the cube (if applicable) or through SAS OLAP Cube Studio. This same method can be used to view the MDX code generated for custom members and sets.
On a more general note, if you want to learn MDX, you can use SAS Enterprise Guide to learn basic MDX syntax by manipulating a cube and viewing the MDX code generated. If you need some help getting started with OLAP – in the To Write or not Write OLAP Code post I talk more about writing OLAP cubes.
Never miss a BI Notes post!
Click here for free subscription. Once you subscribe you'll be asked to confirm your subscription through your email account. You email address is kept private and you can unsubscribe anytime.
Latest posts by Steve Overton (see all)
- BulkLoading with PostgreSQL available in SAS 9.4 - 2013-10-22
- Describe Your Table in SAS to Write the SQL Code - 2013-05-22
- Update Table Metadata Using Base SAS Code - 2012-12-19
- SAS Code: Simple Macro to Benchmark Data Performance - 2012-08-08
- SAS OLAP Cubes: Automatically Collect ARM Performance Logs - 2012-06-18