Developing an OLAP cube, testing in Enterprise Guide or Web Report Studio, and suddenly you begin getting error messages from rebuilding the OLAP Cube stating that it's locked. Now what do you do? Restart the OLAP Server? Well, if you don't have access to the server itself or others are
Author
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
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
Was assisting an individual with an issue on the SAS Discussion Forum and we discovered why some users would not get the prompt to save/view excel content in excel rather than in the web browser. Essentially, the file type options were different for these users. This was causing users to
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
The ODS ExcelXP tagset is pretty powerful stuff. Hidding columns, changing the print layout to landscape, updating the spreadsheet names, defining the default column width and row height, etc - it's all available using options within the ExcelXP setup. So the best thing to do is grab some documentation. Fortunetly,
What if you need someplace to store static files for web consumption. Things that might come to mind: Images HTML Static Title Pages JavaScript PDF Documentation (such as how-to instructions) An ideal place would be a HTML server, since these aren't active files. However in a standard 9.2 installation, there