Database Structure Review

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 nine. This is less than 9.2 database structure review and this lesson. We're gonna discuss the different types of structures and databases that we went over. In this course. One really important structure starts off at the top of the bullet points, and that is the index's basic table component that is critical for quick database queries.
Without the index, you're doing full table scans,
which is very inefficient and scales horribly as more data is added to the database.
Next, our composite indexes helps optimize index implementation for improved performance. This occurs when it makes sense to have multiple indexes on the same table,
and that's kind of related to composite keys. You can break the database into additional logical sections. We saw two examples of that. That was the company I D. In a cume Attica. And that was a school I D. In the database that we developed for tracking students and their scores,
we can use with partitions for even mawr improve part performance. However, with partitions keep in mind, you won't only want to implement them if they make sense to implement, and they make sense when the table is very large. We're talking millions plus of records. Typically,
your biggest performance drag enquiries is going to be related to the index and not to a partition or the lack of a partition.
Next, their data types concept that exists in most programming languages. This really impacts how the engine treats a certain piece of data is the type of data that it is the database engines going to treat a in urge er differently than a string. So you have to be able to indicate which data type
the variable is.
Make sure the column data type makes sense. And finally, that brings us to partitions, partitions, break database tables and two smaller tables, and they're really Onley advisable when you have a very large table.
They're also abstracted from the sequel programmer. You may not even realize you're using a partition without running the explained command, and that brings this lesson review to a close, and I hope to see in the next thank you
Up Next