Clustered Indexes

Video Activity
Join over 3 million cybersecurity professionals advancing their career
Sign up with
Required fields are marked with an *

Already have an account? Sign In »

9 hours 41 minutes
Video Transcription
I welcome back to module five. This is less than 5.2 clustered indexes. There's not gonna be an implementation on this lesson. We're just gonna describe what the difference is between the Clustered Index and a regular secondary index.
So my sequel requires a cluster to index on every table.
My sequel automatically used the primary key as a clustered index. Now, something to keep in mind is this. Convey Ari from database engine to database engine. Microsoft sequel does not require a clustered index on every table, and the impact of the index
can vary from engine to engine as well.
But in general, indexes are just simply used to speed up the debt. Operations on the table,
so clustered indicates that the index architecture is saved on disc in a specific order in a specific pattern that optimizes searching,
you can only have one clustered index.
A non clustered index is not saved on disk and uses memory pointers.
You can have many non closer to indexes, and we saw that when we added indexes to our tables and we added three columns of indexes on some of them.
Index is slow down, right operations the database may need to rearrange the records to maintain the index. So when you insert a new record or you edit an old record
and you edit the index column, the database engine may need to rearrange the records in order to maintain the index in the correct order so this can have an impact on your right performance.
Generally, the actual architecture er off the index may be treated as an abstraction.
And what this means is you do not need to know every detail, off the index architecture and how it operates. You just need to know the appropriate. You use cases when it's appropriate to use an index when it's appropriate. Not whether or not it's better to have it as a clustered index or secondary index, those kind of things.
So let's go ahead and take a look at the summary for this lesson
and to summarize my sequel requires every table has a clustered index.
The primary key is used by default.
All other indexes are considered secondary indexes,
and that completes this lesson, and I hope to see you in the next thank you
Up Next