Timeline for What happens if you stop the IndexOptimize job, because it is running long and causing blocking?
Current License: CC BY-SA 4.0
11 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Oct 19, 2023 at 17:30 | vote | accept | veena ranganath | ||
| S Oct 19, 2023 at 17:30 | vote | accept | veena ranganath | ||
| Oct 19, 2023 at 17:30 | |||||
| S Oct 19, 2023 at 17:30 | vote | accept | veena ranganath | ||
| S Oct 19, 2023 at 17:30 | |||||
| Oct 17, 2023 at 6:48 | answer | added | John K. N. | timeline score: 2 | |
| Oct 16, 2023 at 18:58 | history | edited | Hannah Vernon♦ |
edited tags
|
|
| Oct 16, 2023 at 18:51 | history | edited | Hannah Vernon♦ | CC BY-SA 4.0 |
edited tags, and incorporated detail from comments
|
| Oct 16, 2023 at 16:17 | comment | added | veena ranganath | Thank you ! However If an index maintenance on one of the biggest tables takes over 8-10hrs with potential for blocking, what is the best way forward? kill it and let it rollback or let it run? | |
| Oct 16, 2023 at 16:16 | vote | accept | veena ranganath | ||
| S Oct 19, 2023 at 17:30 | |||||
| Oct 16, 2023 at 15:12 | answer | added | Rayne | timeline score: -4 | |
| Oct 16, 2023 at 14:57 | comment | added | Mainecoon21 | Every rebuild / reorg command is a separate transaction, which means already finished reorgs / rebuilds are committed. If you stop the job the only rollback which happens is on running transaction (one particular index). | |
| Oct 16, 2023 at 14:29 | history | asked | veena ranganath | CC BY-SA 4.0 |