Fragmentation Explained in 20 Minutes

Поділитися
Вставка
  • Опубліковано 26 лис 2024

КОМЕНТАРІ • 9

  • @user-vf3fz7qv6v
    @user-vf3fz7qv6v Рік тому +4

    This was so helpful and easy to understand!

  • @bymchtclk
    @bymchtclk Рік тому +3

    Thx for Great Explanation

  • @BayonetRecon
    @BayonetRecon 2 роки тому +3

    Great presentation!

  • @DavidGallardo-z4s
    @DavidGallardo-z4s 3 місяці тому +1

    Educational and Hilarious!! Thank you so much for the knowledge

  • @killertacsko
    @killertacsko Рік тому +2

    What? Are then page splits caused by inserts our very friends? Or is that treated as an edge case?

  • @thanadonsiringam1400
    @thanadonsiringam1400 Рік тому +2

    Great Explanation

  • @juanpablogallardov
    @juanpablogallardov 2 місяці тому +1

    Why the first page needs to be split? That was never explained.

  • @azihcchidi001
    @azihcchidi001 2 місяці тому +1

    Why was Ian not inserted below Simon in page 2 since attendees name are not in alphabetical order. Inserting it below Simon should not have caused page split

    • @madyarkozhakhmetov5536
      @madyarkozhakhmetov5536 2 місяці тому

      From my understanding, they are talking about an index in a database, so we want to have data stored in an index in some order (like names sorted alphabetically). But the index is stored under the hood in these 8kb pages, and inside the pages SQL Server does not implement a sorted order, it just has a list that holds the sort of the underlying data (idk if other database engines do it like that). So when people query the database, the query optimizer does not want to visit each page and see if record Simon is there (defeats the entire purpose of an index), it wants to immediately find the page with Simon, which means we need to do page splits from time to time to keep data sorted amongst different 8kb pages.