I am aware of 3 layer modeling best practices techniques.
Assuming that 1st layer (import view) is to maintain joins, my "common sense" tells me that the second layer would be a good place to maintain query subject/items names, what to hide and what to show.
Ideally, I would like to have a single master Query Subject that I could maintain Query Items in for all the copies. When snowflake grows to hundreds of query subjects/shortcuts maintenance becomes critical issue.
Any thoughts?
- Alp
1st layer: will be hidden in the package definition, so no use naming here
3rd layer: consists of shortcuts which cannot be changed (only parent can)
Which leaves the 2nd layer ;D
Quote from: blom0344 on 11 Jul 2010 11:04:30 AM
1st layer: will be hidden in the package definition, so no use naming here
3rd layer: consists of shortcuts which cannot be changed (only parent can)
Which leaves the 2nd layer ;D
Let us say we have T1 and T2 in the import view, and there is a join between them.
How do we move/copy T1 and T2 to 2nd layer such way that the relationship is left on the 1st layer only?
Relationship shortcut?
I think I got it now. I might have screwed something else somewhere so I thought that new query subject in a new folder would not reuse the relationship from the underlying query subjects.
Thanks everyone!
- Alp