Time zone considerations

  • Hi Jessica and readers,

    I have an international/multiple time zone client base, do you have recommendations for selecting time zones, and delivering reports to clients respective of their local time?

    Assumptions:

    A client could select a zone other than their own for a given report at run time, however the time should initially default to the clients' local time.

    It looks like System.core.dll has the time information - can it be loaded into a report parameter drop-down? Or, would it be smarter to use a SQL table and a query/sProc ?

    With the fairly recent change in DST date, is there a reliable way to see if it is DST season or not for a given date?

    All reporting data is stored with UTC time

    The client time zone is identified, and UTC offset in minutes including DST

    Thank you in advance for your answers and recommendations.

    Tom

    Tom in Sacramento - For better, quicker answers on T-SQL questions, click on the following...http://www.sqlservercentral.com/articles/Best+Practices/61537/

Viewing 0 posts

You must be logged in to reply to this topic. Login to reply