![]() | |
![]() |
| | Thread Tools | Display Modes |
#1
| |||
| |||
|
#2
| |||
| |||
|
#3
| |||
| |||
|
|
-----Original Message----- Hi Michael, Thanks for your post. According to your description, I unfortunately do not have a clear idea of your problem. If possible, please provide a clear sample on the FoodMart 2000 sample database to describe the problem on your side. Also, please provide the tree structure of the dimension you require. In additional, based on my experience, it is impossible to add a column in the dimension table to create a higher level outside a Parent-Child Dimension. However you can recreate the parent-child relationship by integrating the higher level. Is that what you want? Thanks for using MSDN newsgroup. Regards, Michael Shao Microsoft Online Partner Support Get Secure! - www.microsoft.com/security This posting is provided "as is" with no warranties and confers no rights. . |
#4
| |||
| |||
|
|
My GL Cube has an Accounts DIM that uses a single table that links accountid to parentid. Acutally the columns are accountid, parentid, accountname, categoryid Now this is the problem that I am seeing. I'm using this account table as a normal parent child relationship DIM. But then I want to throw in another table (AccountCategory). This other table can be looked at like the next higher step of the current account DIM. It's basically the top level categories of a balance statement. It seems to be that since each record Account DIM is build a relationship with the parentID and so on, then the category table comes along and tries to restructure the whole thing that way it is told by id/fk. It almost seems like my Top most level AccountCategories should reside in the account table but not allow any child levels to link to it? Any ideas would be great. -mike |
#5
| |||
| |||
|
![]() |
| Thread Tools | |
| Display Modes | |
| |