Every now and then when the applications that use the SQL Server haven't been accessed for a while they get the error "The wait operation timed out". On Error(Sql Exception exception, Boolean break Connection, Action`1 wrap Close In Action) 1742110 System.
When reloading or retrying to access the database it seems to have been "waken up" and is as fast as ever. Win32Exception: The wait operation timed out [Win32Exception (0x80004005): The wait operation timed out] [Sql Exception (0x80131904): Timeout expired.
Host Idle(Object sender, Event Args e) at Microsoft.
Jon Smith relates his quest to find a better answer.
some address doesn't exists in Company Address table.
If I have two DBContext objects from database say Snapshot1, Snapshot2. Sql Exception: Violation of PRIMARY KEY constraint 'PK_Company Address'. Company Address' Your error has got nothing to do with the Db Context objects.
If you don't enable the detection of such conflicts, whoever updates the database last overwrites the other user's changes.
In many applications, this risk is acceptable: if there are few users, or few updates, or if isn't really critical if some changes are overwritten, the cost of programming for concurrency might outweigh the benefit.