Fragmentation Explained in 20 Minutes

Поделиться
HTML-код
  • Опубликовано: 6 янв 2025

Комментарии • 9

  • @user-vf3fz7qv6v
    @user-vf3fz7qv6v Год назад +5

    This was so helpful and easy to understand!

  • @BayonetRecon
    @BayonetRecon 2 года назад +3

    Great presentation!

  • @killertacsko
    @killertacsko Год назад +2

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

  • @bymchtclk
    @bymchtclk Год назад +3

    Thx for Great Explanation

  • @thanadonsiringam1400
    @thanadonsiringam1400 Год назад +2

    Great Explanation

  • @DavidGallardo-z4s
    @DavidGallardo-z4s 5 месяцев назад +1

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

  • @juanpablogallardov
    @juanpablogallardov 3 месяца назад +1

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

  • @azihcchidi001
    @azihcchidi001 4 месяца назад +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 4 месяца назад

      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.