Say I have created a fresh Employee table with a layout similar to the one would normally find in the AdventureWorks database (ID, FirstName, LastName, Address etc. etc.). This table will be one of the most used tables and will contain say roughly 8000-10,000 records. Currently, there are no key constraints defined, though making the EMP_ID as PRIMARY KEY seems to be the obvious for starters. I would like to start creating Indexes for this table.
My question is, Are there any **thumb-rules/best practices**, that define how I should select the Clustered and Non-Clustered Indexes for columns in this table? Clustered - I understand that if the EMP_ID would be made a PRIMARY KEY, then the CLUSTERED INDEX for that column is defined then and there. How shall one recognize which columns would need the non-clustered indexes?
↧