Timeline for Database events that will cause deletion of index
Current License: CC BY-SA 3.0
8 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Aug 18, 2014 at 4:21 | vote | accept | IT researcher | ||
| Aug 17, 2014 at 16:48 | answer | added | Brent Ozar | timeline score: 3 | |
| Aug 17, 2014 at 16:36 | history | tweeted | twitter.com/#!/StackDBAs/status/501044797680123906 | ||
| Aug 13, 2014 at 19:46 | comment | added | Aaron Bertrand | Both SSMS and SSDT will allow you to make changes to a table that will actually require the table be dropped and re-created (not sure about SSDT, but SSMS has an option to allow this under Tools > Options somewhere). Not really a stretch to imagine that a change that could drop / re-create the table would, by extension, re-create all of the indexes. | |
| Aug 13, 2014 at 16:24 | comment | added | Mihai | Maybe it drops a custom named index and recreates it with a default name? | |
| Aug 13, 2014 at 14:14 | comment | added | user507 | Can you specify what tool you are using to make these changes? | |
| Aug 13, 2014 at 14:07 | answer | added | Daniel Hutmacher | timeline score: 3 | |
| Aug 13, 2014 at 13:56 | history | asked | IT researcher | CC BY-SA 3.0 |