optimistic concurrency error with datetimeoffset fields upon update - by d4e666

Status : 


Sign in
to vote
ID 766419 Comments
Status Closed Workarounds
Type Bug Repros 0
Opened 10/6/2012 6:23:28 AM
Access Restriction Public


in my database I have added 3 datetimeoffset(7) fields to record when a record is inserted, updated or deleted. All fields are nullable but date inserted and date updated are set to thefaultvalue getutcdate(). Every time I want to save a record in SSMS I get the notification that data has changed. This seems unlikly since

1. I am the only user on the database
2. The database is local to my system
3. I get this on overy record which seems rather unlikly that someone else is changing my data
Sign in to post a comment.
Posted by Sanjay [MSFT] on 2/6/2013 at 11:51 AM
Hi!, thanks for writing in to Microsoft and reporting this bug.

We took a look at this bug and triaged it against several others and unfortunately, it did not meet the bar to be fixed. While we are closing this bug as 'won't fix', we have taken note of this internally and we will try & incorporate this request when we revisit this functionality in a future release of SSMS.

Sanjay Nagamangalam, SQL Server Manageability