Conformed Dimensions and OWB

Hi, I am trying to use some of my dimensions from one WH Target module in another WH target module.
The simple idea as follows, I am deploying a few new conformed dimensions into my conformed dim WH target. And im puting down a cube into a datamart WH target. This is all in one project. BUT it appears I cannot share, or reference the dims and cubes from other targets :( Even though they will be resolved via thier locations into the same instance.
I would like a statement as this appears to be major missing functionality? (given you can reference tables etc between WH target modules in the same project)
Thanks,
Richard.

Richard,
The current release is indeed restricted to use the dimensions in one module only. This restriction will be removed in the next major release (US summer 2004).
Mark.

Similar Messages

Obiee 11g non-conforming dimensions and nQSError 14025

Does anyone know how to configure the 11g repository for non-conforming dimensions? This worked fine in 10g. I have upgraded the repository to 11g and it doesn't work anymore. I am receiving the error [nQSError: 14025] No fact table exists at the requested level of detail. I have tried building a simple test subject area and testing different configurations, but I have not had any success.
Edited by: user10715047 on Jan 27, 2011 12:33 PM

Ah, I love answering my own questions. :/
The only way I could make this work was a follows...
1. Make sure you have a level-based dimension for each of your logical table dimensions (both conforming and non-conforming).
2. For the fact table measures, set the levels as you did in 10g with the non-conforming dimensions at the Grand Total logical level for each measure.
3. For the fact table LTSs, set the logical level in the Content tab to the dimension's lowest level for each conforming dimension (leave the non-conforming dimensions level blank).
Unfortunately, the query generated in 11g will add an additional sub-query to the mix even though it doesn't appear to have any benefit. Therefore in 10g, if you have two logical fact tables with non-conforming dimensions, three sub-queries were required to create the result set. Two queries for the facts and their related dimensions and a final full outer join to stitch the results together. In 11g, you have one query without the measures, two queries with the measures, and the final outer join.
I am talking to Oracle support about this issue, but I haven't made much progress yet. I asked development to confirm my repository design and they say it checks out. They indicated that the additional query is a design change/enhancement. I am not getting a warm and fuzzy on this one. I'll post back if I make any progress.
Oh, did I mention that this change has broken queries where I attempt to combine fields from two non-conforming dimensions?!? This worked fine in 10g.

Conformed dimension and query multiple fact tables

Hello,
Please if someone can guide me on this requirement.
Requirement - I have a conformed dimension D1 and two fact tables F1 and F2. Both fact tables have many columns so I cannot merge
the two fact tables into one logical table. Currently both these fact tables have logical tables F1 and F2 respectively.
As per design the conformed dimension is a simple logical table in the rpd and not a dimension.
Can someone guide me how should i proceed so that i'll be able to fetch information from both the fact tables?
Edited by: 930542 on Apr 26, 2012 12:28 PM

Hi,
Currently the dimension table is taken as a simple logical table in rpd as it does not have have any levels or hierarchy.
Its a flat dimension. Can you guide me how can I implement a flat dimension in OBIEE? Because this dimension is taken as simple logical table
I am not able to set appropriate level for fac tables. This dimension does not appear in the list of dimensions.

Using two facts of two different star schemas and conformed dimensions

Hi,
I've been working as developer and database designer for years and I'm new to Business Objects. Some people says you can not use two facts of two different star schemas in the same query because of conformed dimensions and loop problems in BO.
For example I have a CUSTOMER_SALE_fACT table containing customer_id and date_id as FK, and some other business metrics about sales. And there is another fact table CUSTOMER_CAMPAIGN_FACT which also contains customer_id and date_id as FK, and some other business metrics about customer campaigns. SO I have two stars like below:
DIM_TIME -- SALE_FACT -- DIM_CUSTOMER
DIM_TIME -- CAMPAIGN_FACT -- DIM_CUSTOMER
Business metrics are loaded into fact tables and facts can be used together along conformed dimensions . This is one of the fundamentals of the dimensional modeling. Is it really impossible to use SALE_FACT and CAMPAIGN_FACT together? If the answer is No, what is the solution?
Saying "you cannot do that because of loops" is very interesting.
Thank you..

When you join two facts together with a common dimension you have created what is called a "chasm trap" which leads to invalid results because of the way SQL is processed. The query rows are first retrieved and then aggregated. Since sales fact and campaign fact have no direct relationship, the rows coming from either side can end up as a product join.
Suppose a customer has 3 sales fact rows and 2 campaign fact rows. The result set will have six rows before any aggregation is performed. That would mean that sales measures are doubled and campaign measures are tripled.
You can report on them together, using multiple SQL passes, but you can't query them together. Does that distinction make sense?

OBIEE 11g 11.1.1.7 NON Confirmed dimensions and facts

Hi All,
In OBIEE 10g if we had non-conformed dimensions we used to work with by defining logical level of the conformed dimensions to grand total and confirmed dimensions to detail in the LTS of the fact table
and also set metrics to grand total level.
But in OBIEE 11g doing same is throwing error
[nQSError: 14025] No fact table exists at the requested level of detail
How do we achieve this?
Regards,
deep

You need to create a complex join with non conformed dimension and the fact with 1=1 and set the logical level of the measure to total for a non conformed dimension.
You can refer: https://s3.amazonaws.com/rmc_docs/biforum2011/Mcquigg_Metadata.pdf

Modelling 2 Fact Tables with Non-Conforming Dimension in OBIEE 11g

Hi all,
I have two fact tables (Fact 1 and Fact 2) and two dimension tables (Product and Rule). The Product dimension table is a conforming dimension and is used in both fact tables, but the Rule dimension is a non-conforming dimension which is used only one fact table. I'm using OBIEE 11g (11.1.1.6.0).
====
Fact 1
====
Sales ID | Product ID | Quantity | Sales Description | Sales Status
S001 | P001 | 100 | bla bla bla bla bla | N
S001 | P002 | 200 | bla bla bla bla bla | N
S002 | P001 | 200 | lab lab lab lab lab | Y
S002 | P003 | 250 | lab lab lab lab lab | Y
Notes for Fact 1:
- One Sales ID can have multiple Product IDs
- Sales Description and Sales Status are the same for one Sales ID (repeating Sales Description and Sales Status for the same Sales ID)
====
Fact 2
====
Sales ID | Product ID | Rule ID | Score
S001 | P001 | R001 | 2
S001 | P001 | R002 | 3
S001 | P002 | R003 | 1
S002 | P001 | R003 | 1
S002 | P003 | R002 | 2
S002 | P003 | R004 | 5
Notes for Fact 2:
- One combination of Sales ID and Product ID can have multiple Rule ID
I'm wondering how best to model these tables so that I can create this report (number of the dimension and fact tables created in the business model, level mapping, aggregation rule, etc)? Any suggestion/advice on how to achieve this?
Sales ID | Product ID | Quantity | Sales Description | Sales Status | Rule ID | Score
S001 | P001 | 100 | bla bla bla bla bla | N | R001 | 2
S001 | P001 | 100 | bla bla bla bla bla | N | R002 | 3
S001 | P002 | 200 | bla bla bla bla bla | N | R003 | 1
S002 | P001 | 200 | lab lab lab lab lab | Y | R003 | 1
S002 | P003 | 250 | lab lab lab lab lab | Y | R002 | 2
S002 | P003 | 250 | lab lab lab lab lab | Y | R004 | 5
Thank you very much!

Hi Dhar, thanks for the suggestions.
I tested what you suggested, but the result is not as per my expectation mentioned above. Here's what I did:
1. In physical layer:
- I joined Fact 1 table with Product dimension table only
- I joined Fact 2 table with Product and Rule dimension tables
2. In business model layer:
- I created 3 logical tables: Fact, Product, and Rule
- The Product table contains the Product ID and Product Name from the Product dimension table in the physical layer
- I created the hierarchy (logical dimension) for Product with only ProductTotal level (as the grand total level) and ProductDetail level that contains Product ID and Product Name
- The Rule table contains the Rule ID and Rule Name from the Rule dimension table in the physical layer
- I created the hierarchy (logical dimension) for Rule with only RuleTotal level (as the grand total level) and RuleDetail level that contains Rule ID and Rule Name
- The Fact table contains 2 logical tables sources: Fact 1 (which logical level in the Content tab is mapped to ProductDetail and RuleTotal) and Fact 2 (which logical level in the Content tab is mapped to ProductDetail and RuleDetail)
- The Fact table contains Sales ID logical column (mapped to both Fact 1 and Fact 2 logical table sources)
- The Fact table also contains Sales Description and Sales Status logical columns (mapped to only Fact 1), which aggregation rule is the default to None
- The Fact table also contains Quantity logical column (mapped to only Fact 1), which aggregation rule is set to Sum
- The Fact table also contains Score logical column (mapped to only Fact 2), which aggregation rule is set to Sum
OBIEE returns the expected result when I retrieve the report:
Sales ID | Product ID | Quantity | Sales Description | Sales Status
However, OBIEE returns an error when I retrieve the reports:
Sales ID | Product ID | Quantity | Sales Description | Sales Status | Rule ID
or
Sales ID | Product ID | Quantity | Sales Description | Sales Status | Rule ID | Score
The error is:
Error Codes: OPR4ONWY:U9IM8TAC:OI2DL65P
State: HY000. Code: 10058. [NQODBC] [SQL_STATE: HY000] [nQSError: 10058] A general error has occurred. [nQSError: 43113] Message returned from OBIS. [nQSError: 43119] Query Failed: [nQSError: 14020] None of the fact tables are compatible with the query request FACT.SALES_STATUS. (HY000)
And the Score column is blank when I retrieved this report:
Sales ID | Product ID | Quantity | Sales Description | Sales Status | Score
Any suggestion anyone? Please help. Thanks a lot!
Edited by: stewartlife on Nov 29, 2012 4:01 PM

Report on non conformed dimension

Hi All,
I am using OBIEE 11.1.1.5
We have 2 facts and 4 dimensions out of which only 1 dimension is conformed. We have a report requirement of using the conformed dimension and filtering based on 2 non conformed dimensions and include the measure from both the facts. When the report is created it is throwing error as
"None of the fact tables are compatible with the query request"
for eg : Let say
F1 --> d1,d2
F2 --> d1,d3,d4
the report has d1.c1,d2.c2,d3.c3,F1.M1,F2.M2 and filter by d2.c2 and d3.c3
Thanks in advance.

Check out patch (bug# 11850704)
Also have you set the level for the non conforming dimension at the highest level of granularity

Two facts with conformed dimension

Starting new thread per Alistair's request :)
I have two facts
Class Enrollment (who is enrolled in which classes)
External Test Scores (who got what score on what exam)
The only dimension they have in common is "Person".
Is it possible to build a presentation layer that includes both facts, the Person dimension, and dimensions that related to one fact but not the other (e.g. dimension "External Test Type" or dimension "Course")?
How would I set up the BI metadata to answer the question:
What was the average grade for Course ABC for students who scored above a 50 on test XYZ?
So far, for External Test Scores fact, I have created hierarchies(/dimensions) for any related dimension tables that didn't already have hierarchies defined. I then went to the Content tab for External Test Scores and set aggregation levels (lowest level for everything related to the fact, "total" level for everything NOT related to the fact).
I put both facts and the "Person" dimension into a presentation folder. I can query test scores ok, but when I add in a simple "Row Count" column from class enrollment, I get no data back.
Do I now go back and do the same Content tab settings for the Class Enrollment fact? My initial attempts at this yielded consistency check warnings of "Logical table source does not join to any fact source".
Huge thanks for suggestions.
-John

Hi John,
I tend to harp on a lot about the need for a hierachy on every logical dim, even just total -> detail. It allows this (non-conformed) approach for starters, also allows another developer to quickly ascertain the relationship between objects.
About the complex joins, I meant do as you will have done for a normal star with just the conformed dims, so thats Foreign keys where applicable in the Phyiscal layer, and Complex joins where applicable in the BMM layer. I just wanted to make a point that you should do this as per a normal normal star schema with fully conformed dimensions, and merely that the none-conformed dimension will only be connected to its relevant fact table - probably didnt need to say it as it may be more confusing!
Your correct with aggregation rules, ideally all objects in a logical fact should have an aggregation rule - otherwise it should be in a logical dimension.
As to the approach, this is the way i've always handled non-conformed dimensions when the requirement is to see both facts on the same report. Our Peak Indicators OBIEE training material on this subject is as follows :
"order" fact table, dimensioned by Date, Customer, Product.
"inventory" fact table dimensioned by Product only.
Report requirement - Show me all orders where the order_qty (order fact) is greater than the total qty in stock (inventory fact)
So like your example, we sum up both qty's and use a where clause to filter only rows where one fact measure is greater than another measure.
Whats the ideal approach ??
If you had control of the ETL perhaps you could seed an 'unknown' record in the non-conforming dimensions, and then reference this on the other fact table, but I'd say the majority of the time, the customer who wants everything by everything in their subject area needs a little education, its really not good for end users having 10's of folders with 10's of columns - we should be creating analysis subject areas to enable the answering of business questions, theres no reason why we cant combine reports from different subject areas on one dashboard page, all using a common set of prompts, but there really isnt a need to give an end user the whole BMM / DW etc in one go.......unless they are paying of course, and after you've tried to educate them they want it there way :-)

Difference between Conformed dimnesion and Role play dimesion

hi,
I am not able to understand difference between Conformed dimension and Role play dimension.. Can anyone please explain the diff between both with real time example.
I am confused with Date Dimension.
Here i encountered, Cube dimension and Database dimension,what is that actually.
Thanks

Hi DevBi,
According to your description, you want to know the difference between database dimension and cube dimension. Right?
A database dimension is a collection of related objects, called attributes, which can be used to provide information about fact data in one or more cubes. What we created in BIDS is database dimension. For example, typical attributes in a product dimension
might be product name, product category, product line, product size, and product price. These objects are bound to one or more columns in one or more tables in a data source view.
Cube dimension is an instance of a database dimension in a cube is called a cube dimension and relates to one or more measure groups in the cube. A database dimension can be used multiple times in a cube. Those referenced and renamed for purpose database dimension
is role-playing dimension. For example, a fact table can have multiple time-related facts, and a separate cube dimension can be defined to assist in analyzing each time-related fact. However, only one time-related database dimension needs to exist, which
also means that only one time-related relational database table needs to exist to support multiple cube dimensions based on time.
Reference:
Role-playing Dimensions
If you have any question, please feel free to ask.
Simon Hou
TechNet Community Support

Problem: two fact tables and one conformed dimension

Hi everyone!
I need to solve this situation:
I have two fact tables, let's say F1 and F2, that are both linked to D1, my conformed dimension
I just need to select fields from D1 but I know that, when querying, OBIEE links it to a fact table anyway..how does it choose the fact table? That is, if I only want fields from D1, does the system queries also from F1 or F2? Is it a random choice?
Is there a way to "force" this choice, telling the system for example to choose only from F1?
Is there a workaround to solve this situation? Remember, I only need fields from D1.
Thanks!!

The solution of your problem is "Implict Fact Column"
Go to presentation layer and double click on your subject area. then you will see Implict fact column option. click on set. give corresponding fact column there( in your case give F1 fact column)
references: http://oracle-bi.siebelunleashed.com/articles/implicit-fact-column/
Thanks
GSR
Edited by: GSR on Mar 20, 2012 3:22 PM

Again: two facts and one conformed dimension

Dear all,
I know this has been asked quite often but I haven't found a solution for my problem here. Believe me I have done a lot of searching across the net ..
What I want to do is the following:
I have two fact tables with a number of common dimensions. A report should show the two facts across these common dimensions.
To keep it simple I start with only one common dimension.
Here's what get's to the db from OBIEE:
*SELECT Revenue."Date (YYYYMMDD)" saw_0, Sales."Day Day Code" saw_1, Revenue."TPV (Total Payment Volume in Millicent [€])" saw_2, Sales.DEBIT_AMOUNT saw_3 FROM "Company KPIs" ORDER BY saw_0, saw_1, saw_3*
Note that *Revenue."Date (YYYYMMDD)"* and *Sales."Day Day Code"* are the same field from the common time dimension. I just put them in different presentation tables for the end users.
TPV and DEBIT_AMOUNT are facts from the two different cubes.
Everything fine, right?
Now I look at the nqquery.log:
RqList
Dim Time.Day Day Code as c1 GB,
Dim Time.Day Day Code as c2 GB,
*Tpv:[DAggr(Cube Revenue.Tpv by [ Dim Time.Day Day Code, Dim Time.Day Id, CUBE_SALES.DEBIT_AMOUNT] )] as c3 GB,*
CUBE_SALES.DEBIT_AMOUNT as c4 GB,
Dim Time.Day Id as c5 GB
OrderBy: c1 asc, c2 asc, c4 asc
now the bold thing looks odd to me. Is he trying to aggregate one cube based on the other? Could be the problem, but where to influence this?
And finally this translates into this query:
WITH
SAWITH0 AS (select distinct T4110.DEBIT_AMOUNT as c1,
T281.DAY_DAY_CODE as c2,
T281.DAY_ID as c3
from
DIM_TIME T281,
CUBE_SALES T4110
where ( T281.DIMENSION_KEY = T4110.DIM_TIME ) ),
SAWITH1 AS (select distinct SAWITH0.c2 as c1,
SAWITH0.c2 as c2,
*cast(NULL as DOUBLE PRECISION ) as c3,*
SAWITH0.c1 as c4,
SAWITH0.c3 as c5
from
SAWITH0)
select SAWITH1.c1 as c1,
SAWITH1.c2 as c2,
SAWITH1.c3 as c3,
SAWITH1.c4 as c4
from
SAWITH1
order by c1, c2, c4
As you see, the tpy ist gone and a NULL appears. That's what I see in the report. TPV is always NULL.
So where did I miss a configuration ???
Thanks, Knut

You only need to set the content levels on the measures themselves when you want non-conformed dimensions in the report, as your working with fully conformed dims just make sure your levels are set on the content tab for each Logical Table source in the Logical fact table. Leave the non-conformed dim hierarchies as blank.
Remember - You should put a hierarchy on each logical dim , even if there is no real hierarchy, just have a total -> Detail.
You should always always always set your content levels for logical table sources, both in Dimensions and Logical fact LTS's.
If they are greyed out, make sure your not in read only, have checked the object out if on-line mode, failing that, perform the changes off-line then re-start your BI Server.

How to import SH Sample Dimensions and Cubes with OWB Client

Hi, is there a functionality to import the Dimensions and Cubes from the sample to reuse and manipulate them within the OWB Client?
I can add Dimensions in the Enterprise Manager but mapping should be difficult- right?
Specs: DB 10g rel2, OWB 10.1.0.4

dimension - either define a table on your own, or use the data modeler and physically define a new dimension.
Cube - same as above.
as for levels and hierarchies, this can also be done in the data modeler. You can specify keys, levels, attributes, measures...all that stuff for dims and facts. There many tabs on the lower half of the dimension modeler screen that control this.
Check out the oracle by examples for easy tutorials.

Conforming and Non-Conforming Dimensions

Hi,
How do we identify conforming and non-conforming dimensions in our OBIEE 11g repository? There are so many of each so was wondering if there is a simple rule i can follow while browsing my repository

To identify them as you are browsing it's not really possible.
From a logical digram you could right click the dimension and select "add joins"... if it adds any facts to the diagram then obviously the dimension is conformed.
Use the Query Repository functionality in the admin tool to identify logical tables that are dimensions, and related to more than one logical table which is a fact.

Filter and non-conforming dimensions

I have a model design which includes three fact tables with non-conforming dimensions. This causes BI to create multiple queries for a report and finally bring the results together using a full outer join at the end. When I attempt to filter on a field from one of the non-conforming dimensions, that filter is not applied at the full outer join step but during an earlier step related to the chosen filter field. This results in more data returning then desired. I need to move the filter to the full outer join step. Here are two sub-optimal methods that I have found to work around the issue.
1. Build the logical query in answers. Then, wrap that query with an outer query and apply the filter to the outer query.
2. Build a minus query in answers that removes the records you don't want to see.
I have seen this issue discussed in other threads, but I haven't found a good solution. Does anyone have any recommendations?
Thank you,
Edited by: user10715047 on May 21, 2010 7:13 AM
Here is a decent description of the problem
http://siebel.ittoolbox.com/groups/technical-functional/siebel-analytics-l/two-fact-tables-and-nonconforming-dimensions-3297052
and this is a better solution than the two I stated above. However, even this solution is not going to be very intuitive for the users
http://siebel.ittoolbox.com/groups/technical-functional/siebel-analytics-l/two-fact-tables-and-nonconforming-dimensions-3298529

i know this is a bit old thread but thought it might be helpful to someone who came across the same issue...
when using Degener@teDimen$ion ( this is !nner joned to FACT tables in BMM) and if any of the dimensions {other than theDegener@teDimen$ion (Let us say Dim X) } have an ()uter join to any of the fact tables, and you were doing your analysis using Degener@teDimen$ion, Dim X, Measure value you will face the following issues.
when filtering the analysis on the ()uter join dimension ( Dim X), the IN filter will not work. Reason is that the filter is getting applied to both the Dimension and FACT tables and the values that exist in Dimension Dim X but not in FACT table wont show up.
The above issue can be fixed by changing the join between the fact and Degener@teDimen$ion from inner to outer.
Please mark if you found this helpful.

Conformed / nonconfirmed dimensions and multiple facts

Hi all,
There have been plenty of posts on this issue, I've read a lot about it, but still can't get this working. We're looking at a basic marketing process where we can track the links that have been clicked in marketing emails that have been sent out. What I have is two fact tables, with one conformed dimension between them, and one of the facts having a non-conformed dimension:
Fact 1 linked to Dim - Links
Fact 2 linked to Dim - Links; Dim - Email Name;
In Fact 1 i have defined a measure that counts the number of links clicked
In Fact 2 i have defined a measure that counts the number of links
So, I can take fields from Dim - Email Name, and Fact 2 and this will correctly show me the number of links in that email. I can add in the Link Name from Dim - Links to give me the detail of the links in the email. However, when I then add the # of links clicked from Fact 2, this is shown as zero. Removing the Email Name will cause the # of clicks to be displayed correctly for each link.
I've read this post here:
report based on 2 different Fact tables
which seems to contain my exact problem, but the solution listed hasn't worked for me. I've created hierarchies, set the LTS of Fact 1 to be Detail for Dim - Links, and the LTS of Fact 2 to be Detail for Dim - Links and Dim - Email Name. This doesn't work. I've then set the LTS of Fact 1 to be Total for Dim - Email Name. this doesn't work. I've then set the LTS for the dimension tables to be detail in each case, and this doesn't work either. My business question is pretty simple - for each email, list the links and how many times that link was clicked.
I've started from scratch, I'm only looking at these 4 logical tables, I've got to the stage where I'm restarting BI after every change but I still can't see the problem. Can anyone give me any guidance please?
thanks
Matt

Hi Wildmight,
apologies for not posting for a few days, I've been out of the country. I've just tried all these, with no joy. At the moment then, I have one single Fact table, with two logical sources, LINKS_FACT and CLICKS_FACT. I've set the LTS for LINKS_FACT to be Email Detail and Link Detail, and the LTS for CLICKS_FACT to be Link Detail and Email Total. The single Fact table now has two measure columns, one a count distinct on linkid and one a count on the clicksid.
When I go into answers, I select an email title of May Newsletter, choose the link name, and then select the # of links and number of clicks. The log for this query is:
-------------------- SQL Request:
SET VARIABLE QUERY_SRC_CD='Report';SELECT "Dim - Emails".TITLE saw_0, "Dim Links"."Link Name" saw_1, "Fact - Links"."# of Links" saw_2, "Fact - Links"."# of Clicks" saw_3 FROM "CRM 2.0" WHERE "Dim - Emails".TITLE = 'May Newsletter' ORDER BY saw_0, saw_1
+++Administrator:2a0000:2a0007:----2009/05/19 10:05:08
-------------------- General Query Info:
Repository: Star, Subject Area: CRM 2.0, Presentation: CRM 2.0
+++Administrator:2a0000:2a0007:----2009/05/19 10:05:08
-------------------- Logical Request (before navigation):
RqList
Dim - Emails.TITLE as c1 GB,
Dim Links.Link Name as c2 GB,
# of Links:[DAggr(Fact - Links.# of Links by [ Dim Links.Id, Dim - Emails.Id] SB Dim - Emails Detail,Dim Links Detail)] as c3 GB,
# of Clicks:[DAggr(Fact - Links.# of Clicks by [ Dim Links.Link Name, Dim Links.Id, Dim - Emails.Id, Dim - Emails.TITLE] )] as c4 GB,
Dim - Emails.Id as c5 GB,
Dim Links.Id as c6 GB
DetailFilter: Dim - Emails.TITLE = 'May Newsletter'
OrderBy: c1 asc, c2 asc
+++Administrator:2a0000:2a0007:----2009/05/19 10:05:08
-------------------- Execution plan:
RqList <<3688>> [for database 3023:15084:CRM,31]
D1.c1 as c1 [for database 3023:15084,31],
D1.c2 as c2 [for database 3023:15084,31],
D1.c3 as c3 [for database 3023:15084,31],
D1.c4 as c4 [for database 3023:15084,31]
Child Nodes (RqJoinSpec): <<3705>> [for database 3023:15084:CRM,31]
RqList <<3573>> [for database 3023:15084:CRM,31]
D1.c2 as c1 GB [for database 3023:15084,31],
D1.c3 as c2 GB [for database 3023:15084,31],
D1.c1 as c3 GB [for database 3023:15084,31],
cast(NULL as INTEGER ) as c4 GB [for database 3023:15084,31],
D1.c4 as c5 GB [for database 3023:15084,31],
D1.c5 as c6 GB [for database 3023:15084,31]
Child Nodes (RqJoinSpec): <<3679>> [for database 3023:15084:CRM,31]
RqList <<3738>> [for database 3023:15084:CRM,31]
count(distinct CRM_LINKS_FACT.ID by [ CRM_LINKS.ID, CRM_EMAILS.ID] ) as c1 [for database 3023:15084,31],
CRM_EMAILS.TITLE as c2 [for database 3023:15084,31],
CRM_LINKS.NAME as c3 [for database 3023:15084,31],
CRM_EMAILS.ID as c4 [for database 3023:15084,31],
CRM_LINKS.ID as c5 [for database 3023:15084,31]
Child Nodes (RqJoinSpec): <<3658>> [for database 3023:15084:CRM,31]
CRM_LINKS T26115
CRM_EMAILS T26105
CRM_LINKS T26129
DetailFilter: CRM_EMAILS.ID = CRM_LINKS_FACT.EMAILID and CRM_EMAILS.TITLE = 'May Newsletter' and CRM_LINKS.ID = CRM_LINKS_FACT.ID [for database 0:0]
GroupBy: [ CRM_EMAILS.ID, CRM_EMAILS.TITLE, CRM_LINKS.ID, CRM_LINKS.NAME] [for database 3023:15084,31]
) as D1
) as D1
OrderBy: c1 asc, c2 asc [for database 3023:15084,31]
+++Administrator:2a0000:2a0007:----2009/05/19 10:05:08
-------------------- Sending query to database named CRM (id: <<3688>>):
select D1.c1 as c1,
D1.c2 as c2,
D1.c3 as c3,
D1.c4 as c4
from
(select distinct D1.c2 as c1,
D1.c3 as c2,
D1.c1 as c3,
cast(NULL as INTEGER ) as c4,
D1.c4 as c5,
D1.c5 as c6
from
(select count(distinct T26129.ID) as c1,
T26105.TITLE as c2,
T26115.NAME as c3,
T26105.ID as c4,
T26115.ID as c5
from
CRM_LINKS T26115,
CRM_EMAILS T26105,
CRM_LINKS T26129 /* CRM_LINKS_FACT */
where ( T26105.ID = T26129.EMAILID and T26105.TITLE = 'May Newsletter' and T26115.ID = T26129.ID )
group by T26105.ID, T26105.TITLE, T26115.ID, T26115.NAME
) D1
) D1
order by c1, c2

Conformed Dimensions and OWB

Similar Messages

Maybe you are looking for