With a clustered index the rows are stored
physically on the disk in the same order as the index. There can
therefore be only one clustered index.
With a non clustered index there is a second list that has pointers to the physical rows. You can have many non clustered indexes, although each new index will increase the time it takes to write new records.
It is generally faster to read from a clustered index if you want to get back all the columns. You do not have to go first to the index and then to the table.
Writing to a table with a clustered index can be slower, if there is a need to rearrange the data.
http://stackoverflow.com/questions/1251636/what-do-clustered-and-non-clustered-index-actually-mean
With a non clustered index there is a second list that has pointers to the physical rows. You can have many non clustered indexes, although each new index will increase the time it takes to write new records.
It is generally faster to read from a clustered index if you want to get back all the columns. You do not have to go first to the index and then to the table.
Writing to a table with a clustered index can be slower, if there is a need to rearrange the data.
http://stackoverflow.com/questions/1251636/what-do-clustered-and-non-clustered-index-actually-mean
No comments:
Post a Comment