Included are two quick references to tuning OLAP Cubes: Server Tuning Information ~ http://support.sas.com/documentation/cdl/en/biasag/61237/HTML/default/viewer.htm#a003145996.htm Cube Tuning Information ~ http://support.sas.com/documentation/cdl/en/olapug/59574/HTML/default/viewer.htm#a002605609.htm Also, you can add aggregations to the OLAP cube to improve performance. As mentioned in my earlier post, you should consider doing Advanced Aggregation Tuning to provide presummarized measures of various
Tag: OLAP
In SAS OLAP the N-WAY summarization is created by default, however you have the option to not create the N-WAY & as I highlighted in a prior post, not creating it changes your OLAP type to either a HOLAP or ROLAP. But the real question is what the heck is this
As mentioned in my previous post, there is the need to move OLAP cubes around. Switching to one schema to another via SAS OLAP Cube Studio is straightforward enough, but what if you need to move it from one Business Intelligence Environment to another (a Development BI Server to a
SAS recommends building OLAP Cubes on a separate 'non-production schemas' because cube building can be resource intensive and time consuming. Each OLAP Server can be defined to one & only schema at a given time, therefore you will need to setup the architecture to include another OLAP Server & Schema
When creating an OLAP Cube from a Star Schema table, the Dimensions / Hierarchies created must be free of all blanks. This is because the name is used as a table alias in the SQL Join. The obvious error in the resulting code example below: proc sql; create table geography
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
Business problem: By default, OLAP cubes calculate aggregations at each possible intersection of levels in one or more dimensions. However, there are situations where aggregations cannot be completed on the fly for all intersections within the cube due to business rules for some data levels. Also, the source data table
Out of the box, no members of the SASUSERS group are allowed to create OLAP Cubes. In 9.2, the error message states "The security package failed while authenticating a user", included below is a screen shot. The fastest way to remediate this is to allow the SASUSERS group to have
For OLAP Cube Developers to gain access to SAS 9.2, two items: 1. Authorizing Access to SAS OLAP Servers from SAS http://support.sas.com/documentation/cdl/en/biasag/61237/HTML/default/a003311504.htm "Users of SAS OLAP Cube Studio need readMetadata and writeMetadata permissions. To read and update the authorizations for SAS OLAP Servers, follow these steps: 1.Open SAS Management Console.
I was struggling with a calculated member that completes a distinctcount of members in a dimension, the performance was simply unacceptable. After attempting several other measures such as count(), processing changes on the source data, etc, I sent out a msg on Twitter asking for advice. Once again, why aren't