Ran into an interesting bug today. I’m working with a client that’s using .net 4.5.1, EF 6.1.3, and is in the process of upgrading to SQL Server 2016. When we did the update, we suddenly had entities that were being detected as being different, even though the data was exactly the same. This was causing us to get unexpected concurrency exceptions. The following sql would be generated by entity framework: exec sp_executesql N'UPDATE [dbo].[MyTable] SET [StateLastChangedDate] = @0 WHERE (([Id] = @1) ......