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
One of the sweet new capabilities in 9.2 OLAP for cube developers is the Cube Job that is automatically created for each new cube. The job is used as a interface mechanism to schedule the cube refresh code without manually retrieving the PROC OLAP code and customizing it for scheduling which we "old"
I mentioned back in 2008 that Web Reports with OLAP source can drill-through to detail (or display the raw data records for the corresponding cross tabular cell) only after the source information map has drill-through to detail enabled. Well, there are several other areas that also could disable this capability
In order to make the OLAP drill through data available as data tables in the Enterprise Guide, all you need to do is change the option to automatically insert the results as a data set in the project. This is extremely useful if part of your workflow includes navigating through
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
In the past couple months, this scenario has occurred twice. So thought I'd share a quick remedy ~ and save for my future reference when this occurs again :). In Star Schemas, there are sometimes occasions where the data quality isn't exactly perfect. And sometimes, for some users/companies, this is
OLAP Calculated Members need to be tested to ensure that the numbers are correct in various tools. What we recently found was that the member tested properly in the OLAP Studio View Cube but then in Web Report Studio, the measure wasn't correct. Essentially, it was calculating the custom measurement
In 9.2, OLAP Cubes can be updated incrementally. This is awesome, as you then don't have to worry about users locking your cube by closing the Web Report Studio window or leaving their EG session running. However, at the same time, this can cause the size of space an OLAP
In SAS 9.2, OLAP Member Level Security became that much easier to implement. From SAS Management Console, an administrator can navigate directly into the OLAP Cube Dimension, add a user, grant explicit 'Read' access and click a button to get a snazzy interface to add read or deny security. The
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
