Thanks for the replies, sorry that it took me a while to reply back. I went for using a conversion table as johnherman had suggested and then created views onto each time zone, seems to be working well.
Thanks for your reply, all dates in the operational database are already in UTC, I'm looking into ways of viewing a date dimension in multiple time zones. I suppose I'm looking for validation of the proposal I posted up in comparison to other techniques such as:
1) multiple date foreign keys in...
After thinking about this approach some more I have had to alter the concept. The only way it can be viable is if there is an hour column that holds the UTC hours for every day, so 0 to 23 per day. In this case then the date dimension would actually be replaced with a DateByHours dimension...
I am currently implementing a data warehouse and I'm following the Kimble approach of having a separate date dimension which is currently the UTC date. I have hit a slight wall when it comes to time zones as the clients will be wanting to view their data in each respective zone.
This is not a...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.