Re: 2 fields in same level should display on same row

#1

How a level can be defined by two columns

--
Posted via http://dbforums.com

#2

The ID should probably be the key of the Region level. Some client tools
then might already allow you to do this. Otherwise you could define ID as a
member property as well, and then some more client tools would allow you to
generate such a report. You don't want Region ID and Region Name to be
seperate Dimensions or Levels because they have a 1-to-1 relationship and
having both verses just one does not change the dimensional size and shape
of the cube.

Hope this helps,
- Matt Carroll
--
This posting is provided "AS IS" with no warranties, and confers no rights.

"devnoronha" <member33654 (AT) dbforums (DOT) com> wrote

Quote:

i have a table which has
10 NY
20 LA
30 London
i need to display the sales in each city
10 NY 500
20 LA 600
30 London 300

10 and NY are on the same level . but when i select like
select {[Region].[Region ID].Members, [Region].[Region Name].Members} on
rows it displays

10 500
20 600
30 300
NY 500
LA 600
London 300

is the solution in the 'select' statement or in the cube design ?
Thanks

--
Dev Noronha

Posted via http://dbforums.com

Thread Tools
Show Printable Version Email this Page
Display Modes
Linear Mode Switch to Hybrid Mode Switch to Threaded Mode

Re: 2 fields in same level should display on same row

microsoft.public.sqlserver.olap microsoft.public.sqlserver.olap

Re: 2 fields in same level should display on same row - 08-15-2003 , 03:03 PM

Re: 2 fields in same level should display on same row - 08-15-2003 , 08:53 PM