Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
Hi All,
I have a FACT Table with below information.
DateUID | Sales |
1 | 1000 |
1 | 1000 |
1 | 156 |
1 | 26 |
1 | 258 |
2 | 285 |
3 | 100 |
3 | 1458 |
3 | 265 |
4 | 2558 |
4 | 1245 |
4 | 2655 |
4 | 254 |
Date dimension table line below
DateUID | Date | TimeSlotHour | Time Zone PST Date | Time Zone IST Date |
1 | 3/3/2016 | 1 | 3/3/2016 | 3/4/2016 |
2 | 3/3/2016 | 2 | 3/3/2016 | 3/4/2016 |
3 | 3/3/2016 | 3 | 3/3/2016 | 3/4/2016 |
4 | 3/3/2016 | 4 | 3/3/2016 | 3/4/2016 |
5 | 3/3/2016 | 5 | 3/3/2016 | 3/4/2016 |
6 | 3/3/2016 | 6 | 3/3/2016 | 3/4/2016 |
7 | 3/3/2016 | 7 | 3/3/2016 | 3/4/2016 |
8 | 3/3/2016 | 8 | 3/3/2016 | 3/4/2016 |
9 | 3/3/2016 | 9 | 3/3/2016 | 3/4/2016 |
10 | 3/3/2016 | 10 | 3/3/2016 | 3/4/2016 |
11 | 3/3/2016 | 11 | 3/3/2016 | 3/4/2016 |
12 | 3/3/2016 | 12 | 3/3/2016 | 3/4/2016 |
13 | 3/3/2016 | 13 | 3/3/2016 | 3/4/2016 |
I need to link DateUID.... when i am linking it is Many to One relation (Fact to Dim), that is fine.
However i am dividing Date dimension table based on Timezones (like PST and IST) and concatenating them... so that i will show all timezone in a list box for selection.
Now that problem is it is many to many relation and while loading... it is taking much much time... of course i dont even know whether it will work out or not.
Can anyone suggest how can we fulfill this requirement?
Thanks in advance.
My Apologies Bill... Just understand that the problem is there in key field name, which was not correct...
This is solved and working fine. Thanks for your help.