Timeline for SQL Server SSMS - Edit 200 rows functionality - is it possible for two or more people to alter each other's work using this functionality?
Current License: CC BY-SA 4.0
4 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jan 11, 2022 at 7:37 | vote | accept | AcePL | ||
| Jan 11, 2022 at 7:37 | comment | added | AcePL | Thank you. This seems to confirm empirically what I suspected. Yes, the fun part is that SSMS's UI is just nice interface, somewhat cumbersome, with vanilla SQL behind it. And it confirms that two people can overwrite each other's work if not careful with WHERE. | |
| Jan 10, 2022 at 11:41 | comment | added | Dan Guzman |
"What SSMS did was to submit an UPDATE with a WHERE clause for each column". Adding that this technique is called optimistic concurrency (as opposed to pessimistic locking). If the table has a rowversion column, that could be used instead of comparing every column but SSMS doesn't seem to leverage that.
|
|
| Jan 10, 2022 at 10:10 | history | answered | Tibor Karaszi | CC BY-SA 4.0 |