Quantcast
Channel: SQL Server Analysis Services Forum
Viewing all articles
Browse latest Browse all 2472

Two DSV relationships and attribute names

$
0
0

Hi all,

I have a case whereby we have, for example, a dimension like:

Customer -> Territory    ->Region

-> Secondary Territory ^

Basically, a customer belongs to a territory, and a secondary territory.  Any territory can be a primary or a secondary territory of a customer.

In my customer dimension, I create two attributes using TerritoryId and SecondaryTerritoryId as the key columns.  The problem is, however, that when I use the "Territory" table in the data source view to link it through, the name (with a Territory.Name as the NameColumn value) is wrong.  It always uses the first relationship in the DSV (the "primary" territory) to link through which I understand.

Now, the obvious thing would be to change the Customer table to a named query and bring in the SecondaryTerritoryName into that query.  My problem is, I can't use named queries for any of these tables because I use ROLAP aggregations and to use those, I need to have regular tables (otherwise it tried to create an indexed view on a subquery, which doesn't work).

Without literally replicating the Territory table (including its data), is there any way to make this work?


Viewing all articles
Browse latest Browse all 2472

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>