[Mondrian] Restrict data being accessed by mondrian via filters

[Julian Hyde]

Easiest thing would be to create a "SELECT ... WHERE" view in the database
and base Mondrian's dimension on that.
 
It is possible to base a dimension on a query, but Mondrian doesn't parse
the query, it just includes it as a subquery in the FROM clause. Most
databases are fine with that, but it's possible that your database would pay
a performance penalty.
 
The other option, which may or may not work, depending on your model, is to
add an extra level at the top of your dimension, whose key is the column
that you want to filter your dimension table on. 
 
Hope that helps.
 
Julian


  _____  

From: mondrian-bounces at pentaho.org [mailto:mondrian-bounces at pentaho.org] On
Behalf Of Constant2k
Sent: Monday, December 07, 2009 1:56 PM
To: mondrian at pentaho.org
Subject: [Mondrian] Restrict data being accessed by mondrian via filters


Dear Mondrian experts, 


I'm evaluating Mondrian with a the TPC-DS schama (scale = 100GB .
largest table hold 400 millions of lines )

Is is possible to restrict the scope of each dimension via a WHERE clause?
Do I need to know how to code a "schema processor" to achive this?

Thanks and Regards,

Constant2k

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.pentaho.org/pipermail/mondrian/attachments/20091207/fa845fbb/attachment.html