Timeline for How do I automate converting heaps into clustered indexes?
Current License: CC BY-SA 3.0
8 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jun 22, 2019 at 3:00 | history | tweeted | twitter.com/StackDBAs/status/1142265973673725952 | ||
| May 22, 2019 at 18:33 | answer | added | Tony Lucero | timeline score: -1 | |
| Apr 13, 2017 at 12:42 | history | edited | CommunityBot |
replaced http://dba.stackexchange.com/ with https://dba.stackexchange.com/
|
|
| Oct 22, 2012 at 17:53 | vote | accept | Hannah Vernon♦ | ||
| Oct 3, 2012 at 13:36 | comment | added | Darin Strait | Do non-clustered indexes exist on the heap tables? One of those index's columns might be good for a clustered index. How big are the tables? If they are "too large" relative to the power of the server, you might want to drop the existing indexes, add the cluster index and then add back those indexes that you dropped. As Martin points out, it's hard to write code that will make a decision that would be pretty easy for a human. For 40 tables, I'd just write it out, maybe use some kind of templating for the rote parts. Maybe it would take a day to write, and I'd know more about my db. | |
| Oct 3, 2012 at 12:46 | answer | added | Thomas Stringer | timeline score: 8 | |
| Oct 3, 2012 at 11:50 | comment | added | Martin Smith | What exactly are you trying to automate? The decision as to which column(s) to make as the CI keys seems best to left to a human to me except if you have a truly representative workload in which case maybe you can let the DTA have a go at it. | |
| Oct 3, 2012 at 5:33 | history | asked | Hannah Vernon♦ | CC BY-SA 3.0 |