I am having problems with my MSAS db conversion. I posted a question earlier
and didn't really get an answer to help me, so now that I can provide a
little more information, I was hoping that someone would be able to help me
find the problem.

The problem appears to be with the conversion of heirarchical dimmensions.
From what I can see it appears that they were converted correctly, but when I
look at the data they are not correct. Below are some samples of what I have
in MSAS 2000 and 2005

From MSAS 2000
-------------------------------------
All Locations
Posicharge Mrb
(blank)
060/068
Posicharge Stock
(blank)
.022
...
From Browsing this Dimension in 2000 Cube Editor:
Cube Name:
CM340
Dimension:
Location
- Location
--Sub Location

From MSAS 2000
-------------------------------------
From Dimension Editor in VS for Locations Dimension under cube CM340:

===============================================
=Attributes: = Heir. & Levels = Data Source View
= ===============================================
=Locations = Locations =
=
= Location = -Location = ========
=
= Sub Location(key) = --Sub Location = = dbo.dim =
=
= = <new level> = = ....
= =
= = = =
..... = =
= = = =
..... = =
= = =
======== =
= = =
=
= = =
=
===============================================
From Browsing this Dimension in 2005 Dimension Editor:
All Locations
Posicharge Mrb
060/068
Posicharge Stock
(blank)
.022
...


Any help is greatly appreciated! If you need further clarification, let me
know.

Jason

Hi Jason,

What does the dimension table data look like, for the hierarchy that you
listed; and what does "(blank)" mean?
Does this migrate to a strong hierarchy in AS 2005?


- Deepak

Deepak Puri
Microsoft MVP - SQL Server

*** Sent via Developersdex http://www.developersdex.com ***

Deepak,
I think I have found the problem. It appears to do with uniqueness of
member keys. AS2005 requires that all attributes have unique keys. Whereas
AS2000 lets you specify AreMemberKeysUnique=false on a level, in which case
the server implicitly concatenates the keys from the upper levels. You have
to do this manually in AS2005.

I am in the process of editing the dimensions that have problems in AS2005
and going to each attribute that I am having uniqueness problems with, and
then add additional columns to make each attribute unique. In the Property
Panel, selecting the KeyColumns field and adding the additional columns from
the heirarchy to make the key unique.


--
Jason


"Deepak Puri" wrote:

Yup. We call adding additional key fields a "key collection". RDBMS' call it
a concatenated key.
--
Dave Wickert [MSFT]
dwickert (AT) online (DOT) microsoft.com
Program Manager
BI Systems Team
SQL BI Product Unit (Analysis Services)
--
This posting is provided "AS IS" with no warranties, and confers no rights.


"JasonDWilson" <JasonDWilson (AT) discussions (DOT) microsoft.com> wrote