Tag Info

New answers tagged

0

If you will always have SchoolId then you could benefit from making the clustered index a composite key of SchoolId, Id as you won't have to have an additional index on SchoolId to avoid a table scan. Not having the additional index will let Inserts/Updates/Deletes complete faster as the transaction only has to update one index. You may find as you create ...


3

Are there exceptions to the above clustered index rules? The general guidance for selecting a clustered index is good, but there are sometimes additional considerations to be taken into account. Occasionally, these extra factors can be more important than the general 'rules'. Your scenario is somewhat "special" in that you have a very wide table, with a ...



Top 50 recent answers are included