Effect of "lost update" transaction on ms sql server is not possible under any circumstances?

Question

SQL Server

On Wikipedia, the transaction isolation level article describes the "lost update" effect.
At the same time, it is also written there that the lowest isolation level guarantees the absence of lost updates. Considering that any queries, as far as I know, on ms sql server are executed inside transactions (even queries not explicitly wrapped in a transaction will be executed in a transaction), it turns out that a "lost update" in ms sql server is not possible in principle? That is, for example, running a bunch of updates in parallel in ms sql server that increment the same field, I don’t even have to worry about the possibility of a “lost update”, despite the warning on Wikipedia (perhaps this should be take a steam bath users of other subds in which there are no transactions, or autotransactions?)?

Answer 1

There will be a so-called. "deadlock" , you can read more on the topic "lock", for example on habré