what is the use of first mixed extent in 2016 and why keeping blank all 8 pages

  • As we know before 2016 , when we enter first record it get stored in page inside first shared\mixed extent.
    But after 2016, we insert any record its not get stored in first 8 pages.
    My question is why we keep blank first 8 pages and start filling data from Uniform extents?

  • RAJIVR67 - Sunday, July 8, 2018 2:48 AM

    As we know before 2016 , when we enter first record it get stored in page inside first shared\mixed extent.
    But after 2016, we insert any record its not get stored in first 8 pages.
    My question is why we keep blank first 8 pages and start filling data from Uniform extents?

    Before 2016, this behavior was controlled for the SQL Server instance by the trace flag 1118, general purpose is to minimize contention in extent allocation.
    😎 
    In 2016 and later, one can use alter database to set the is_mixed_page_allocation_on value.

Viewing 2 posts - 1 through 1 (of 1 total)

You must be logged in to reply to this topic. Login to reply