Timeline for Why might a table scan have a huge I/O Cost?
Current License: CC BY-SA 3.0
9 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Apr 18, 2012 at 16:37 | vote | accept | Joshdan | ||
| Apr 18, 2012 at 7:43 | answer | added | John Sansom | timeline score: 3 | |
| Apr 18, 2012 at 5:26 | comment | added | Remus Rusanu |
You can do an ALTER TABLE ... REBUILD
|
|
| Apr 18, 2012 at 4:24 | comment | added | Joshdan | @Remus Hmm... "trivial" or not, that definitely looks like the answer. It appears I have 25 million ghost records in that table. Assuming I am too impatient for the ghost cleanup, would the best way to go be to copy what little is left to a new table, and drop the existing one? | |
| Apr 18, 2012 at 2:07 | history | tweeted | twitter.com/#!/StackDBAs/status/192434254326665216 | ||
| Apr 18, 2012 at 1:32 | comment | added | Remus Rusanu | @Eric: I notices that now an answer like that gets automatically flagged as 'trivial answer' and is moved to comments. | |
| Apr 17, 2012 at 23:36 | comment | added | Eric Higgins | ^^^ Should be answer | |
| Apr 17, 2012 at 22:58 | comment | added | Remus Rusanu | Ghosted Records. See SQL Server “empty table” is slow after deleting all (12 million) records | |
| Apr 17, 2012 at 22:48 | history | asked | Joshdan | CC BY-SA 3.0 |