![]() | |
![]() |
| | Thread Tools | Display Modes |
#1
| |||
| |||
|
#2
| |||
| |||
|
|
Hi, I have a problem designing a cube in SSAS 2000. I would like to know, if it's possible, how can I define an outer join between a fact table and a dimension table (left outer join or right outer join). In the Cube Editor I can only make a join, an inner join, and I don't want to lose any information from the fact table. Thanks |
#3
| |||
| |||
|
#4
| |||
| |||
|
#5
| |||
| |||
|
#6
| |||
| |||
|
|
Hello, Can you explain further? you wrote: The easy way: add an "unknown" member in the dimensions where you'll don't have information and convert "null" values to the "unknown" value in the fact tables. in my case I lways reserved the key column "-1" to handle unknown members and my fact tables are loaded with -1 instead of null values, which result in a good data quality, a fast load of the cube and a better control of the data presented. Are you modifying the underlying table of the dimension tables? |
#7
| |||
| |||
|
|
Hello, Can you explain further? you wrote: The easy way: add an "unknown" member in the dimensions where you'll don't have information and convert "null" values to the "unknown" value in the fact tables. in my case I lways reserved the key column "-1" to handle unknown members and my fact tables are loaded with -1 instead of null values, which result in a good data quality, a fast load of the cube and a better control of the data presented. Are you modifying the underlying table of the dimension tables? |
#8
| |||
| |||
|
|
adding the "-1" key in the dimension table can be done in the table himself or in the DSV. instead-of using the table, create a named view and do a union all select col1, col2, col3.... from table union all select -1, 'Unknown', 'Unknown'.... for your fact table, add a new calculated column where you do something like: newcolumnkey = isnull(mycolumnKey,-1) (you convert nulls to -1) and you have do the cleansing without changing the tables, but I reconnad to clean your fact and dimension table. When I load my datawarehouse, I always replace NULL values by "-1" I prefer this because I can control the labels more easier and with more detail then AS can do. "Sonya" <sam (AT) samNOSPAM (DOT) com> wrote in message news:18ece85996e944b182377581fbc8db65 (AT) ureader (DOT) com... Hello, Can you explain further? you wrote: The easy way: add an "unknown" member in the dimensions where you'll don't have information and convert "null" values to the "unknown" value in the fact tables. in my case I lways reserved the key column "-1" to handle unknown members and my fact tables are loaded with -1 instead of null values, which result in a good data quality, a fast load of the cube and a better control of the data presented. Are you modifying the underlying table of the dimension tables? |
#9
| |||
| |||
|
|
The fact table is clean but I got a new business rule to include another dimension table and when I do it creates duplicates. When I run the query QA, I used left join to remove the problem but I can't do this in AS. I was trying to come up with a way to perform this action. "Jéjé" wrote: adding the "-1" key in the dimension table can be done in the table himself or in the DSV. instead-of using the table, create a named view and do a union all select col1, col2, col3.... from table union all select -1, 'Unknown', 'Unknown'.... for your fact table, add a new calculated column where you do something like: newcolumnkey = isnull(mycolumnKey,-1) (you convert nulls to -1) and you have do the cleansing without changing the tables, but I reconnad to clean your fact and dimension table. When I load my datawarehouse, I always replace NULL values by "-1" I prefer this because I can control the labels more easier and with more detail then AS can do. "Sonya" <sam (AT) samNOSPAM (DOT) com> wrote in message news:18ece85996e944b182377581fbc8db65 (AT) ureader (DOT) com... Hello, Can you explain further? you wrote: The easy way: add an "unknown" member in the dimensions where you'll don't have information and convert "null" values to the "unknown" value in the fact tables. in my case I lways reserved the key column "-1" to handle unknown members and my fact tables are loaded with -1 instead of null values, which result in a good data quality, a fast load of the cube and a better control of the data presented. Are you modifying the underlying table of the dimension tables? |
#10
| |||
| |||
|
|
ooohhh.... its a many-many issue. in AS2005 there is an easy solution: create a fact which contain the duplicated rows, and the other fact which is NOT linked to the new dimension you want (so there is no duplicate) create a new group of measures based on the new fact, link the new dimension to this measure group (create only 1 and hidden measure "countofrow" if you don't want to do anything else with this measure group) in the dimension mapping you see the new dimension linked to the new measure group and not linked to the old measure group. now, click to link the new dimension to the old measure group and select the "many many" relationship. its done. read this: http://www.sqlserveranalysisservices...mensionsV2.htm "SAM" <SAM (AT) discussions (DOT) microsoft.com> wrote in message news:AACEC896-8DFD-4EC6-BE75-56BC4BE1F9CF (AT) microsoft (DOT) com... The fact table is clean but I got a new business rule to include another dimension table and when I do it creates duplicates. When I run the query QA, I used left join to remove the problem but I can't do this in AS. I was trying to come up with a way to perform this action. "Jéjé" wrote: adding the "-1" key in the dimension table can be done in the table himself or in the DSV. instead-of using the table, create a named view and do a union all select col1, col2, col3.... from table union all select -1, 'Unknown', 'Unknown'.... for your fact table, add a new calculated column where you do something like: newcolumnkey = isnull(mycolumnKey,-1) (you convert nulls to -1) and you have do the cleansing without changing the tables, but I reconnad to clean your fact and dimension table. When I load my datawarehouse, I always replace NULL values by "-1" I prefer this because I can control the labels more easier and with more detail then AS can do. "Sonya" <sam (AT) samNOSPAM (DOT) com> wrote in message news:18ece85996e944b182377581fbc8db65 (AT) ureader (DOT) com... Hello, Can you explain further? you wrote: The easy way: add an "unknown" member in the dimensions where you'll don't have information and convert "null" values to the "unknown" value in the fact tables. in my case I lways reserved the key column "-1" to handle unknown members and my fact tables are loaded with -1 instead of null values, which result in a good data quality, a fast load of the cube and a better control of the data presented. Are you modifying the underlying table of the dimension tables? |
![]() |
| Thread Tools | |
| Display Modes | |
| |