Anonymous

My feedback

  1. 35 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    under review  ·  10 comments  ·  SQL Server » Bugs  ·  Flag idea as inappropriate…  ·  Admin →
    Anonymous supported this idea  · 
  2. 56 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  SQL Database  ·  Flag idea as inappropriate…  ·  Admin →
    Anonymous shared this idea  · 
  3. 465 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    34 comments  ·  SQL Database  ·  Flag idea as inappropriate…  ·  Admin →
    Anonymous supported this idea  · 
  4. 4 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  SQL Database  ·  Flag idea as inappropriate…  ·  Admin →
    Anonymous supported this idea  · 
  5. 87 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    8 comments  ·  SQL Database  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    Anonymous commented  · 

    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.

    Anonymous supported this idea  · 

Feedback and Knowledge Base