Timeline for duplicate key error creating unique index on temp, SQL Server 12.0.5589 bug?
Current License: CC BY-SA 4.0
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Nov 8, 2018 at 13:17 | answer | added | Josh Darnell | timeline score: 2 | |
| Nov 7, 2018 at 19:04 | comment | added | Aaron | I just realized the CI on the temp table didn’t include both columns. That puts it right back on the dirty reads and the order of operations that the application that is making updates to the table is doing. I’m deleting my answer as it doesn’t apply until the CI is extended to include the other column. | |
| Nov 7, 2018 at 18:02 | comment | added | Laughing Vergil | Have you considered using SNAPSHOT isolation? It uses tempdb and row versioning, but your reads are guaranteed to not be blocked by writes. Check How to Choose Between RCSI and Snapshot Isolation Levels for a good discussion that is a clearer explanation of these isolation levels than anything else I have read (yet). | |
| Nov 7, 2018 at 17:40 | history | edited | Hannah Vernon♦ | CC BY-SA 4.0 |
improved formatting
|
| Nov 7, 2018 at 17:34 | history | asked | Jeremy Giaco | CC BY-SA 4.0 |