team;

i have an incorrect join that is like stuck in analysis services.

I can't kill the join, i can't make the join valid.

This isn't working.

Just because 2 fields have the same name, it doesn't mean that they have to
be joined-- what am i doing wrong?

Aaron,

Are you deleting the join in the cube editor and it keeps returning
even after you've saved the cube?

Steve

Here is a detailed repro on what is happening to me:

ACCOUNT dimension is a snowflake, 3 levels deep. It has these tables:
ACCOUNT, EPLAN_GROUP, EPLAN_SUBGROUP. These tables are already in the cube,
as I used to have this as 2 seperate dimensions, Account and Eplan. I
realized that it made sense to change this to one hierarchy-- because that
is how the data is shaped.

I changed the Account dimension in AM and then I deleted the EPLAN
dimension. This left the extra EPLAN tables still in the cubes. For some
reason-- the account dimension isn't present in this cube; and it won't let
me add it-- because of this incorrect join. it shows an extra join on
the dimension (it is auto-joining based on field names-- almost every table
has these fields) so I right-click delete the incorrect join and it gives me
this warning

if you change of remove the join between the tables 'EPLAN_GROUP' and
'ACCOUNT' the following objects that depend on the current join with be
removed. Dimensions: account. Do you want to continue?

If I hit Yes, it removes the shared dimension, if i hit No it won't remove
the join. This join cannot be present. Imagine having a 'DateEntered' field
on both dimension tables and it was joining on that-- that is basically what
I am encountering. But AM won't let me fix this. So what am I supposed to
do? So I need to wrap these 3 dimension tables into a view and make it
back into a star dimension??? I don't use views for dimensions; I swear it
effects performance-- ON CUBE BROWSING, I SWEAR... but especially on cube
processing.

There isn't anywhere for me to fix the SQL for this join. It doesn't give
me enough control to fix the join.



"Steve McHugh" <steve (AT) oneleg (DOT) net> wrote

Looks like the trouble i had recently....if I wanted to use the same
relational tables
once more in another dimension I had to make a view of these tables so they
weren't
called the same - I even had to alter the name of the ID in this view.

As you say AS really don't like the same objects / ID's in different
dimensions.


"aaron kempf" <aarkem (AT) safeco (DOT) com> wrote

i got around it by changing to a star-schema against a view.

it's just frustrating that this company-- microsoft-- is the most powerful
company ever... and they can't fix these sort of things.

I mean-- they won't fix these sort of things.

They have $70 billion in their savings account-- but they can't afford to
fix problems in their products.

If I was Ballmer, I would fire about 1/3 of the whole company-- their track
record for usability is awful.

Test the products before you sell them
Test the products before you sell them
Test the products before you sell them
Test the products before you sell them.


"Michael Vardinghus" <michaelvardinghus (AT) hotmail (DOT) com> wrote

Well perhaps it isn't an error....perhaps its quite intentional so that the
performance of AS will work best ?

This is a very large topic with lots of litterature and I for one cannot say
that I have the whole picture yet....

They do testing of products - they even let people like us participate in
beta testing so I don't agree with you opinions....why not look at what has
been created instead of looking at some small details which can be solved
using another technique.


"aaron kempf" <aaron_kempf (AT) hotmail (DOT) com> wrote