Search results for query: *

Hi nlim, thanks for the very good answer! Another solution could be to have MSTR include the distinct ID (i.e. customer ID) and then perform the calculation on the OLAP engine, but I don't have a clue how to achieve this or if consolidations would work together with it. As only consolidations...

Hi all, we're facing frequent problems with calculating count distincts, and I think they could be of greater value to be discussed here (sorry if this seems too enthusiastic to some of you, but believe me if you're not aware of this you'll run into problems) First, consider a DWH where you...

Z3, thanks for your help, yes this looks like the SQL I want... And indeed, OLAP services seems to be the problem, I'll check with support ... Thanks a lot for your answer!

Hi all! We currently phase the same problem - but in a different configuration. Our ETL part resides on a Unix box within an Oracle database. Has anyone ever implemented a "trigger event" function from Unix? Maybe even out of Oracle? I do see two possible ways to go: 1) Use the...

reisw, First of all: Thanks a lot for your hints :). I tried to unchecked the table option "The key defined is the true key for the warehouse table". No change to the query - even after purging the cache and logging off and on again. Just to be sure again: DEGDIM_INVOICE is created...

Yes, there is a relation to product and warehouse via their dimension key in the same fact table. But as you alrady assumed: we do have seperate lookup tables for them. Since none of the attribute for product and warehouse are not used in the query I would not expect to see those DimKey's in...

Hi reisw, here is a sample query: select a12.CUSTOMER CUSTOMER, a11.DEGDIM_INVOICE INVOICE_NUMBER, sum(a11.TOTAL_SALES) WJXBFS1 from FACT_SALES a11, DIM_CUSTOMER a12, FACT_SALES a13 where a11.DIMKEY_CUSTOMER = a12.DIMKEY_CUSTOMER and a11.DEGDIM_INVOICE =...

Hi Z3, thanks for your reply! some more details on the attribute which is causing the problem: - it's based on a CHAR column in the fact table (and some aggregates) - no other lookup table there ...! - no relationships defined, not even to a set of dimension keys in the fact table (I tried but...

Hi all, I'm trying to implement a degenerated dim. such as an invoice number, where you don't have a dimension table but just a single field which can easily be stored in the fact table only. I tried to define it as an attribute, but it joins the fact table against itself ... any ideas what is...

Hi there, I'm interested if there's a solution to this: Say you have an attribute in which you expect a sequence number with a stepping of 1. Now I'd like to report on all the gaps in this sequence between the min and the max existing in the elements list. Example: "sequence&quot...