MySQL: INDEXES are awesome

#mysql #tutorial #course
-- INDEX (BTree data structure)
-- Indexes are used to find values within a specific column more quickly
-- MySQL normally searches sequentially through a column
-- The longer the column, the more expensive the operation is
-- UPDATE takes more time, SELECT takes less time
-- Single column index
CREATE INDEX last_name_idx
ON customers (last_name);
-- Multi column index
CREATE INDEX last_name_first_name_idx
ON customers (last_name, first_name);

[@BroCodez]

-- INDEX (BTree data structure)
-- Indexes are used to find values within a specific column more quickly
-- MySQL normally searches sequentially through a column
-- The longer the column, the more expensive the operation is
-- UPDATE takes more time, SELECT takes less time
-- Single column index
CREATE INDEX last_name_idx
ON customers (last_name);
-- Multi column index
CREATE INDEX last_name_first_name_idx
ON customers (last_name, first_name);

[@nagendradevara1]

❤

[@innocentomoyibo6312]

I hit the like button before I even watched the video because I knew I wasn't going to be disappointed, it's Bro code after all😂

[@vinayaksingh524]

Hey bro ! Loving the new style of content+ thumbnails , it's really neat and to the point.

[@cymaco_ytb8620]

super cette petite vidéo notamment nous y retrouvons une explication très développé et simple ce qui facilite l'aprentissage, merci de subvenir a nos besoins d'aprentissage et continuez vos vidéos pour apprendre plus au jeunes comme moi.

[@pegalolz]

thanks brother im presenting a cybersecurity project in 4 days and i needed this

[@amanthakur6913]

You have really came a long way bro

[@geniushomwetv9793]

Well Explained❤

[@UddhikaIshara]

Thank you

[@diegogouveia1137]

Hey bro, nice content

[@maximillianquaife-larsen3799]

Best video on the ropic

[@Esteapen]

This is so cool but I have some questions:
1.) What if the table often UPDATES and also SEARCHES? Does it still applicable to add an INDEXED COLUMN?
2.) If I were to UPDATE a table with one of its column was INDEXED (but I'm not going to UPDATE the INDEXED column nor use it for WHERE condition) does it still affects the processing time?
I hope someone will help me clarify. Thank you in advance!

[@DroisKargva]

1) You have to find balance between search and update. Typically in data warehouse you would want more indexing (because its used for SELECT statements) while you would want less indexing for Database. Ultimately you would want to find balance in your scenario.
2) This is good question. I am not quite sure. Would like to know answer as well.

[@shriharikulkarni07]

Can you please explain indexes on joins and group by etc

[@jagannathgaidhani5333]

your MySQL workbench platform UI looks very clean! how did you do that ? mine looks very unappealing
can you plz tell me settings options ?

[@tomatentheo7198]

Is it possible to crate a Index over multiple tables?
For Example if i had two tables with unique keys and aggregate those to get a faster result set?

[@junior.santana]

How would you "aggregate" those tables?
An index is created per table, but let's say you want to perform any kind of Join then you can (likely should) create an index on the secondary keys to help MySQL find the records on the "joined" table.
If you want to perform a Union then they are actually two queries being executed in a sequence, both of which could have their own specific keys.
I'm not sure about what cenario you're thinking about, let me know if that helps

[@Hallandfan847]

yoo 2nd

[@georgemilev4831]

I like the video but it would have been great if you showcased it with a bigger dataset.

[@calebadinfono7758]

The like counter was at 666. Had to drop a like to change that. Thanks for the video🙏

[@feliciaf8]

so if i use only the first name, then the last_name_first_name_idx won't be used?