Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations MikeeOK on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
2 Queries Intersection ... 1
- Thread starter Benouche
- Start date
Hello Benouche,
Based on the SQL the 2 queries amount use the code to create a freehand SQL dataprovider on the RDBMS you are running the queries on:
Select a,b,c from d where .......
INTERSECT
Select a,b,c from e where .......
Restriction is that all objects in the select list are compatible.
Hard to imagine to get the intersect using separate universes, let alone at the report level (linked queries are treated as full outer joins through linking dimensions) T. Blom
Information analist
Shimano Europe
tbl@shimano-eu.com
Based on the SQL the 2 queries amount use the code to create a freehand SQL dataprovider on the RDBMS you are running the queries on:
Select a,b,c from d where .......
INTERSECT
Select a,b,c from e where .......
Restriction is that all objects in the select list are compatible.
Hard to imagine to get the intersect using separate universes, let alone at the report level (linked queries are treated as full outer joins through linking dimensions) T. Blom
Information analist
Shimano Europe
tbl@shimano-eu.com
-
1
- #3
You can do it at the report level if you have a measure in each data provider.
Build a filter that filters on a dimension. DEFINE the filter as =not isnull(<measure from DP1>) and (not isnull(<measure from DP2))
What remains are the records that have values from both queries. Steve Krandel
BASE Consulting Group
Build a filter that filters on a dimension. DEFINE the filter as =not isnull(<measure from DP1>) and (not isnull(<measure from DP2))
What remains are the records that have values from both queries. Steve Krandel
BASE Consulting Group
- Status
Similar threads
- Locked
- Question