Skip to content

Update pages-and-extents-architecture-guide.md #10300

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
culushishui wants to merge 1 commit into
base: live
Choose a base branch
from
+1 −1
Open

Update pages-and-extents-architecture-guide.md #10300

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion docs/relational-databases/pages-and-extents-architecture-guide.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -70,7 +70,7 @@ For example, a table can be created with two columns: one **varchar(7000)** and

When a table or an index has **varchar**, **nvarchar**, **varbinary**, **sql_variant**, or CLR user-defined type columns that can exceed 8,060 bytes per row, consider the following:

- Moving large rows to another page occurs dynamically as rows are lengthened based on update operations. Update operations that shorten rows can cause them to be moved back to the original page in a `IN_ROW_DATA` allocation unit.
- Moving large colums to another page occurs dynamically as rows are lengthened based on update operations. Update operations that shorten rows can cause them to be moved back to the original page in a `IN_ROW_DATA` allocation unit.
Copy link
Contributor

@dimitri-furman dimitri-furman Mar 15, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
- Moving large colums to another page occurs dynamically as rows are lengthened based on update operations. Update operations that shorten rows can cause them to be moved back to the original page in a `IN_ROW_DATA` allocation unit.
- Moving columns to another page occurs dynamically as rows are lengthened based on update operations. Update operations that shorten rows can cause them to be moved back to the original page in a `IN_ROW_DATA` allocation unit.


This data movement results in extra disk I/O. Query processing operations such as sorts or joins on large records that contain row-overflow data might be slower.

Expand Down