How can we improve Azure SQL Database?

← SQL Database

Support DateTimeOffset data type in memory-optimized tables

Add support for DateTimeOffset data type in memory optimized tables

66 votes
Vote
Sign in
(thinking…)
Sign in with: Microsoft
Forgot password?
Create a password
Signed in as (Sign out)
Close
Close
You have left! (?) (thinking…)
Scott shared this idea  ·   ·  Flag idea as inappropriate…  ·  Admin →

7 comments

Attach a File
Sign in
(thinking…)
Sign in with: Microsoft
Forgot password?
Create a password
Signed in as (Sign out)
Close
Close
Submitting...
An error occurred while saving the comment
  • Jeff Cox commented  ·   ·  Flag as inappropriate

    DatetimeOffset is the recommended date format, but Not supported or even considered for InMemory Tables... what?

  • D. Casado commented  ·   ·  Flag as inappropriate

    Need this too!! We are using DateTimeOffset in all our date columns and we are now evaluating In-Memory feature of SQL Server.

    NOT SUPPORTED :(

  • Pooyan commented  ·   ·  Flag as inappropriate

    it's been already 4 years since the introduction of Memory Optimized tables and still some features and data types are not supported. Rowversion is the one I need here.

  • Johan Mulder commented  ·   ·  Flag as inappropriate

    DatetimeOffset is the recommended date format as per MS documentation , but not supported in-memory. As most tables have a date value, in-memory becomes a pipe dream for most developers.

    Plse reconsider.

  • Anonymous commented  ·   ·  Flag as inappropriate

    Rowversion and/or Timestamp would be a good idea too. At least then we could consider using the Azure Mobile Apps SDK. Now they don't work with in memory-optimized tables.

  • Jos de Bruijn commented  ·   ·  Flag as inappropriate

    Thanks for submitting the suggestion. We don’t have this planned as an improvement at this time, but we’ll update you if this changes.

SQL Database

Categories

Feedback and Knowledge Base

(thinking…)
Hosted by UserVoice