Manual Level in Dimension using MS OLAP

Manual Level in Dimension using MS OLAP

Post by siddharth » Tue, 31 Dec 2002 15:28:38



Hi!
Is there a way using which I can create a Manual Level in a Dimension.

I have a Salesperson Dimension table containing the names of all sales
persons. What I would like to do is to create a level like Alphabetical
Listing and have categories like A - D, E - H, ...etc. The salesperson
with First name starting would be in A - D, starting with H in E - H
and so on.

I can do this by creating an additional column in my salesperson table
but is there a way I can create this OLAP Services manually. Tools like
Cognos and Biz. Objects can do this.

Thanks for all your inputs in advance.

Seasons Greetings,

Siddhartha

--
Posted via http://dbforums.com

 
 
 

Manual Level in Dimension using MS OLAP

Post by George Spoffor » Wed, 01 Jan 2003 01:32:27


You could manually add a "grouping" level above the Salespersons. Just add
a level above SalesPersons and in the "Advanced" properties tab set
Grouping property to "Automatic". AS2K will automatically put the
salespeople in different groups with names like "Abbot - Franklin", "Fraser
- Hewlitt", and so on.  This will make your dimension a "changing"
dimension, with some negative performance impact on processing and querying
the cubes if the groups change, so it's not necessarily the best idea.

It's pretty easy to get the first letter of names, so you can end up with
A, B, C, ... . Add a level above Salespersons, based on the same name and
key columns as Salespersons, and then edit the level's Member Key Column
property in the "Basic" properties tab. If you click twice inside the key's
text area (not double-click) you can begin to edit its text. Change it to
the expression

Left ("dimTable"."SalespersonName", 1)

Edit the Member Name Column to be the same thing.

I would definitely mark this level as having unique names and keys as well,
assuming there is no higher level.

HTH


> Hi!
> Is there a way using which I can create a Manual Level in a Dimension.

> I have a Salesperson Dimension table containing the names of all sales
> persons. What I would like to do is to create a level like Alphabetical
> Listing and have categories like A - D, E - H, ...etc. The salesperson
> with First name starting would be in A - D, starting with H in E - H
> and so on.

> I can do this by creating an additional column in my salesperson table
> but is there a way I can create this OLAP Services manually. Tools like
> Cognos and Biz. Objects can do this.

> Thanks for all your inputs in advance.

> Seasons Greetings,

> Siddhartha

> --
> Posted via http://dbforums.com

--
George Spofford
Microsoft MVP
Chief Architect / OLAP Solution Provider
DSS Lab
http://www.dsslab.com

ISVs & IT organizations: Find out how DSS Lab can speed your development!

 
 
 

Manual Level in Dimension using MS OLAP

Post by siddharth » Wed, 01 Jan 2003 17:03:17


Hi George!
Thanks for your prompt reply. The solutions provided by you didnt work
in my case there are multiple levels in the salesperson dimension. So
how can I set all the members to be unique? Is there something, which I
am missing?

Also is there a way by which I can create Custom Level Sales Person
Type and create Members like Internal Sales Persons and External
Agents and assign the respective salespersons to the same?

Thanks for your inputs in advance.

Cheers,
Sid

--
Posted via http://dbforums.com

 
 
 

Manual Level in Dimension using MS OLAP

Post by George Spoffor » Sat, 04 Jan 2003 00:33:10


You weren't able to add a level for the first letter of the last name, or
was that not an adequate solution?

To use a "grouping" level, the next level down requires unique member keys.
If you can't provide them, then it is true that you cannot use a grouping
level. There is almost always a way of constructing them, but I don't know
whether you have the means to. For example, the salesperson names may not
be unique, but the salesperson keys in a source system will certainly be
unique. As you load new salespersons into a dimension table, you can
maintain a column of unique id numbers (perhaps as an IDENTITY column), and
then use that column for your key.

Sales Person Type with Internal and External requires adding an appropriate
column to your dimension table and populating it.

HTH


> Hi George!
> Thanks for your prompt reply. The solutions provided by you didnt work
> in my case there are multiple levels in the salesperson dimension. So
> how can I set all the members to be unique? Is there something, which I
> am missing?

> Also is there a way by which I can create Custom Level Sales Person
> Type and create Members like Internal Sales Persons and External
> Agents and assign the respective salespersons to the same?

> Thanks for your inputs in advance.

> Cheers,
> Sid

> --
> Posted via http://dbforums.com

--
George Spofford
Microsoft MVP
Chief Architect / OLAP Solution Provider
DSS Lab
http://www.dsslab.com

ISVs & IT organizations: Find out how DSS Lab can speed your development!
 
 
 

1. Cell-Level security in MS OLAP under MS SQL 7.0

hi all good people
thanks for an answer in advance
I know that in OLAP under MS SQL 2000 by defining a custom rule for
cell secirity , you can specify which cube cells can be accessed by
end user in the role. For example, i can grant rule weather end user
can read/view salary measures or not.

I have heared that MS SQl 7.0 service pack 3.0 for OLAP improve
cell-level securuty (see description of MS SQl 7.0 service pack 3.0
for OLAP http://support.microsoft.com/support/kb/articles/Q274/7/98.ASP
)

Is it right? Does it mean that since the service pack 3.0 have been
instolled you can specify which cube cells can be accessed by end user
in the role??

Any information reg this question are very welcome.

2. Error message when executing .EXE - VFP 3.0

3. OLAP Dimensions with no levels of hierarchy

4. Index name (hind_405_4)

5. Formating a level of the time dimension in MS Analysis Services

6. Extended Stored Proc (SQLSERVER 70)

7. Q: BrioQuery, MS OLAP Cubes: Dimension/Measure Access Control

8. Solution required

9. Cognos & MS OLAP Services - large dimension

10. Time dimension not sorted in MS Olap

11. What is the size of the largest dimension that MS OLAP supports

12. Big dimensions / MS OLAP

13. Cognos & MS OLAP Services - large dimension