Skip to content

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

Open
culushishui wants to merge 1 commit intoMicrosoftDocs:livefrom
culushishui:patch-5
Open

Update pages-and-extents-architecture-guide.md#10300
culushishui wants to merge 1 commit intoMicrosoftDocs:livefrom
culushishui:patch-5

Conversation

@culushishui
Copy link
Contributor

Are you sure that is moving row ?

Are you sure that is  moving row ?
@prmerger-automator
Copy link
Contributor

@culushishui : Thanks for your contribution! The author(s) and reviewer(s) have been notified to review your proposed change.

@learn-build-service-prod
Copy link
Contributor

Learn Build status updates of commit 49aa2aa:

✅ Validation status: passed

File Status Preview URL Details
docs/relational-databases/pages-and-extents-architecture-guide.md ✅Succeeded

For more details, please refer to the build report.

Copy link
Contributor

@dimitri-furman dimitri-furman left a comment

Choose a reason for hiding this comment

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

Thank you for catching this inaccuracy, we will update the article.

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

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants