@petertrast It's not really a case of loving Clustered Tables.
It's more a case of every table MUST have one and you should only remove them if they cause performance problems.
Side effect of not having Clustered indexes are forwarding pointers which result in RID lookups. Very poor DB designs result in this.
And try to not create a clustered index which results in insertion sorts. Insert should append to end of table, i.e. Key should be ever increasing.
Hjominbonrun 10 months ago
Nice subject choice! I love clustered indexes!! :)
petertrast 1 year ago
@petertrast It's not really a case of loving Clustered Tables.
It's more a case of every table MUST have one and you should only remove them if they cause performance problems.
Side effect of not having Clustered indexes are forwarding pointers which result in RID lookups. Very poor DB designs result in this.
And try to not create a clustered index which results in insertion sorts. Insert should append to end of table, i.e. Key should be ever increasing.
Hjominbonrun 10 months ago
Nice subject choice! I love clustered indexes!! :)
petertrast 1 year ago