Timeline for PAGELATCH_EX occures in update query with UPDLOCK, READPAST
Current License: CC BY-SA 3.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Oct 15, 2015 at 3:47 | vote | accept | Backs | ||
| Oct 15, 2015 at 3:47 | comment | added | Backs | I'll follow your advice in future. But now I've just added filtered index, because I can't change message processing code right now. | |
| Oct 14, 2015 at 16:38 | history | edited | Hannah Vernon♦ | CC BY-SA 3.0 |
edited body
|
| Oct 14, 2015 at 13:31 | comment | added | Remus Rusanu | @MaxVernon that's what I mean by 'keep events, not state'. After the event is consumed (ie. message is deleted), if you wish to keep the history (=state), keep it whenever you wish. | |
| Oct 14, 2015 at 13:04 | comment | added | Hannah Vernon♦ | If queue messages must be retained, they can be moved into a table on different filegroup, preferably on a different set of disks, correct? | |
| Oct 14, 2015 at 7:13 | history | answered | Remus Rusanu | CC BY-SA 3.0 |