Timeline for Is a clustered index on a child table in a parent/child relationship the most optimal index?
Current License: CC BY-SA 3.0
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Feb 6, 2015 at 21:05 | vote | accept | JDT | ||
| Feb 6, 2015 at 14:51 | history | tweeted | twitter.com/#!/StackDBAs/status/563711666551275520 | ||
| Feb 6, 2015 at 14:40 | history | edited | user1822 | edited tags | |
| Feb 6, 2015 at 14:37 | answer | added | Thomas Kejser | timeline score: 4 | |
| Feb 4, 2015 at 22:01 | comment | added | JDT | They do not HAVE to be, but if they are not they would be made unique internally by SQL Server (which is the database I'm working with so YMMV for other systems...). There is some overhead for this so I would try to avoid it. See: stackoverflow.com/questions/4332982/… | |
| Feb 4, 2015 at 21:41 | comment | added | a1ex07 | Why do you think clustered index must be unique? | |
| Feb 4, 2015 at 20:22 | history | asked | JDT | CC BY-SA 3.0 |