i have googled a bit for this but fear i am missing an important keyword.
What methods are used to handle concurrent updates in sql server? That is, two users editing the same 'thing'.
The way ravenDB does it [1] looks good to me. What support is there for approaches of this type (using etags) in sql server?
Could you also discuss what you allow the end users to see/do? eg are they given options to 'ignore clash and override'
[1]: http://ravendb.net/docs/http-api/http-api-comcurrency
