Showing posts with label relationship. Show all posts
Showing posts with label relationship. Show all posts

Thursday, March 29, 2012

Auto fill in colums trough foreign key relationship

Hi,
I have a table users where there is a user_id and an department column.
Also i have a table called KRS where there are the same columns, when a userid is given i want to auto fill in the departmentid,
Can someone help me with this?
Cheers WimYou want help creating a denormalized database?

[sigh...]

If you absolutely need to do this, you can accomplish it through an INSERT trigger on your KRS table.

Why are you duplicating data like this?|||You want help creating a denormalized database?

[sigh...]

If you absolutely need to do this, you can accomplish it through an INSERT trigger on your KRS table.

Why are you duplicating data like this?I keep trying to shoot myself it the foot, but the rifle wobbles when I pull the trigger. Can one of you guys hold it for me?

I actually thought about trying to formulate a reply to this question, but nothing I wrote seemed fit to post. I'm thinking that a VIEW would make life a lot easier in the long run, what do you think?

-PatP

Saturday, February 25, 2012

attribute relationship modelling by BIDS

Hi,

litle question about modelling attribute relationships on dimensions with >=50 Attributes?

As far as I know it is only possible in the treeview of BIDS to model attribute relationships, but what if I have already 50 Attributes and want to drag an attribute to an attribute thats already as much down that i cannot see it - if you drag an attribute the view does not scroll down like excel or some other appliation while you are at the boarder of the view.

Is there any other way do add some attribute relationships? (not code, not programming)

Hannes

You can right click on an attribute in the tree view and then choose "copy". Then you can go down to the attribute that you want to relate the first attribute to and "Paste" on the "<new attribute relationship>" drop zone.

HTH,

Steve

Attribute relationship doestn't exisits between

I am using SSAS 2005 (64bit)
i have client table
Dimension is
ClientShortCode (First letter of clientcode)
ClientCode
ClientName
In Dataview
Related clientcode to clientcode in fact table.
Before SP2 installation works fine, when i browse the dimension it looks like
A
ACC
Axxxx (name of client)
ABI
Abi....
....
....
....
L
LUJACK
LUMBERJACKS
After installing SP2, it give warning message
Attribute relationship doestn't exisits between one or more levels in this
hierachy
Is there any thing we need to do after installing SP2
any soultions or idea
Thanks in advance
kk
Well, did you check the atribute relationships in the dimension?
MC
"Kalyan" <Kalyan@.discussions.microsoft.com> wrote in message
news:43D2E6FA-B462-4132-9336-944AA350F07A@.microsoft.com...
> I am using SSAS 2005 (64bit)
> i have client table
> Dimension is
> ClientShortCode (First letter of clientcode)
> ClientCode
> ClientName
>
>
> In Dataview
> Related clientcode to clientcode in fact table.
>
> Before SP2 installation works fine, when i browse the dimension it looks
> like
>
> A
> ACC
> Axxxx (name of client)
> ABI
> Abi....
> ....
> ....
> ....
>
> L
> LUJACK
> LUMBERJACKS
>
>
> After installing SP2, it give warning message
> Attribute relationship doestn't exisits between one or more levels in this
> hierachy
>
> Is there any thing we need to do after installing SP2
> any soultions or idea
>
> Thanks in advance
> kk
|||I gave relationship in data view, can you explain me how to check
atribute relationships in the dimension?
Thanks
Kalyan
"MC" wrote:

> Well, did you check the atribute relationships in the dimension?
>
> MC
>
> "Kalyan" <Kalyan@.discussions.microsoft.com> wrote in message
> news:43D2E6FA-B462-4132-9336-944AA350F07A@.microsoft.com...
>
>
|||You need to go to the dimension editor in BIDS and check on the atribute
relationships for the atributes involved.
MC
"Kalyan" <Kalyan@.discussions.microsoft.com> wrote in message
news:D993701D-45E5-454A-A28D-84D33EE515B0@.microsoft.com...[vbcol=seagreen]
> I gave relationship in data view, can you explain me how to check
> atribute relationships in the dimension?
> Thanks
> Kalyan
> "MC" wrote:

Attribute relationship doestn't exisits between

I am using SSAS 2005 (64bit)
i have client table
Dimension is
ClientShortCode (First letter of clientcode)
ClientCode
ClientName
In Dataview
Related clientcode to clientcode in fact table.
Before SP2 installation works fine, when i browse the dimension it looks lik
e
A
ACC
Axxxx (name of client)
ABI
Abi....
...
...
...
L
LUJACK
LUMBERJACKS
After installing SP2, it give warning message
Attribute relationship doestn't exisits between one or more levels in this
hierachy
Is there any thing we need to do after installing SP2
any soultions or idea
Thanks in advance
kkWell, did you check the atribute relationships in the dimension?
MC
"Kalyan" <Kalyan@.discussions.microsoft.com> wrote in message
news:43D2E6FA-B462-4132-9336-944AA350F07A@.microsoft.com...
> I am using SSAS 2005 (64bit)
> i have client table
> Dimension is
> ClientShortCode (First letter of clientcode)
> ClientCode
> ClientName
>
>
> In Dataview
> Related clientcode to clientcode in fact table.
>
> Before SP2 installation works fine, when i browse the dimension it looks
> like
>
> A
> ACC
> Axxxx (name of client)
> ABI
> Abi....
> ....
> ....
> ....
>
> L
> LUJACK
> LUMBERJACKS
>
>
> After installing SP2, it give warning message
> Attribute relationship doestn't exisits between one or more levels in this
> hierachy
>
> Is there any thing we need to do after installing SP2
> any soultions or idea
>
> Thanks in advance
> kk|||I gave relationship in data view, can you explain me how to check
atribute relationships in the dimension?
Thanks
Kalyan
"MC" wrote:

> Well, did you check the atribute relationships in the dimension?
>
> MC
>
> "Kalyan" <Kalyan@.discussions.microsoft.com> wrote in message
> news:43D2E6FA-B462-4132-9336-944AA350F07A@.microsoft.com...
>
>|||You need to go to the dimension editor in BIDS and check on the atribute
relationships for the atributes involved.
MC
"Kalyan" <Kalyan@.discussions.microsoft.com> wrote in message
news:D993701D-45E5-454A-A28D-84D33EE515B0@.microsoft.com...[vbcol=seagreen]
> I gave relationship in data view, can you explain me how to check
> atribute relationships in the dimension?
> Thanks
> Kalyan
> "MC" wrote:
>

Friday, February 24, 2012

Attribute Relationship ?

I think understand how and why we need to setup attribute relationship but I'm probably missing one important thing here...

If I have the following hierarchies in my dimension:

Circulaire > Segment > Promotion

Circulaire > Promotion

Logically I should have defined my attribute relationship like this:

Circulaire

Segment

- Circulaire

Promotion

- Segment

- Circulaire

Promotion Key

- Promotion

This result in the following error:

This dimension contains one or more redundant attribute relationships. These relationships may prevent data from being aggregated when a non-key attribute is used as a granularity attribute in a cube. Verify the following relationships and delete those that are not needed: [Code Promotion] -> [Promotion - Circulaire].

What is the best practice to manage those issues with attribute relationship? I want to make sure that all my hierarchies are designed for best performance.

On the same note how should we set-up attribute relationship when multiple hierarchies are using the same level in different order?

LEVEL 1 > LEVEL 2 > LEVEL 3 > LEVEL 4

LEVEL 1 > LEVEL 3 > LEVEL 2 > LEVEL 4

thanks,

In the 1st scenario, since Segment directly relates to Promotion and Circulaire directly relates to Segment, relating Circulaire to Promotion is redundant. This is similar to a Year->Month->Day hierarchy, where relating Year to Day directly would be redundant.

In the 2nd scenario, I assume that there are 2 alternate hierarchies for user navigation. They can't both be natural (strong) hierachies (unless there is a strict 1:1 relationship between Level 2 and Level 3 members). So attribute relationships should only reflect strict functional dependencies, not navigational convenience. This paper discusses attribute relationships in more detail:

http://www.sqlserveranalysisservices.com/OLAPPapers/AttributeRelationships.htm

|||Thank you