locked
Timestamp in Table Storage shows 6 hours ahead RRS feed

  • Question

  • From @seannewcome via Twitter:

    Why does my South Central, Azure Table Storage put a timestamp on inserted Entities that is 6 hours ahead of Central Time? The location is "South Central US" and there are no properties or settings in the Azure Portal for adjusting the time.

    Thanks!

    @AzureSupport

    Monday, February 15, 2016 10:15 PM

All replies

  • When an Entity is inserted into Azure Table Storage at 3 PM Central Time, the Timestamp has a value of 9 PM.
    Monday, February 15, 2016 10:29 PM
  • Table Storage timestamps are in UTC. It doesn't matter what region it is in. Your application should read it as UTC time and convert it to local time if necessary.

    • Proposed as answer by Anthony_Chu Monday, February 15, 2016 10:57 PM
    Monday, February 15, 2016 10:57 PM
  • By default table storage, take the server time and store it in UTC, when you access it, you need to convert back the time. But, in case of custom columns, this does not happen, the time you enters is stored as it is, not converted.

    Lets say you have two methods in webservice that takes student marks and store in table storage.

    public string storeStudentMarks(int marks){

    var time=datetime.now;

    storemarksintablestorage(marks,time);

    }

    and another that take time of entry in param from users,

    public string storeStudentMarks(int marks, Datetime time){

    storemarksintablestorage(marks,time);

    }

    In case 1, Server time will be stored in the table storage, while in second case, it will store the time that is passed on from the service itself.

    Friday, June 30, 2017 4:06 PM