Support DateTimeOffset data type in memory-optimized tables
Add support for DateTimeOffset data type in memory optimized tables
why is it so hard to do DateTimeOffset in memory?.. seems like an arbitrary limitation and one that is a blocker for this feature
Was getting amped with the options for InMemory Tables.... only to have my dreams CRUSHED by learning that DateTimeOffset data types are not supported.
Jeff Cox commented
DatetimeOffset is the recommended date format, but Not supported or even considered for InMemory Tables... what?
I'm stuck. All our "date" columns are datetimeoffset!
Casado, Daniel commented
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 :(
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
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.
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
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.