Skip to content

Conversation

@moematsuo
Copy link
Contributor

No description provided.

@prmerger-automator
Copy link
Contributor

@moematsuo : 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 8f3dfff:

✅ Validation status: passed

File Status Preview URL Details
docs/database-engine/configure-windows/enable-the-lock-pages-in-memory-option-windows.md ✅Succeeded

For more details, please refer to the build report.

@ktoliver ktoliver requested a review from Copilot October 30, 2025 15:19
Copy link
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

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

Pull Request Overview

Updates documentation to mention SQL Server Configuration Manager as an alternative method for enabling the Lock pages in memory policy, in addition to the existing Windows Group Policy tool method.

  • Added SQL Server Configuration Manager as an available tool since SQL Server 2019
  • Maintained existing documentation about Windows Group Policy tool

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

> Locking pages in memory might boost performance when paging memory to disk is expected. For more information, see [Lock pages in memory (LPIM)](server-memory-server-configuration-options.md#lock-pages-in-memory-lpim).
Use the Windows Group Policy tool (`gpedit.msc`) to enable this policy for the account used by [!INCLUDE [ssNoVersion](../../includes/ssnoversion-md.md)]. You must be a system administrator to change this policy.
Use the Windows Group Policy tool (`gpedit.msc`) or SQL Server Configuration Manager(since SQL Server 2019) to enable this policy for the account used by [!INCLUDE [ssNoVersion](../../includes/ssnoversion-md.md)]. You must be a system administrator to change this policy.
Copy link

Copilot AI Oct 30, 2025

Choose a reason for hiding this comment

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

Missing space before the opening parenthesis. It should be 'SQL Server Configuration Manager (since SQL Server 2019)' for proper formatting consistency.

Suggested change
Use the Windows Group Policy tool (`gpedit.msc`) or SQL Server Configuration Manager(since SQL Server 2019) to enable this policy for the account used by [!INCLUDE [ssNoVersion](../../includes/ssnoversion-md.md)]. You must be a system administrator to change this policy.
Use the Windows Group Policy tool (`gpedit.msc`) or SQL Server Configuration Manager (since SQL Server 2019) to enable this policy for the account used by [!INCLUDE [ssNoVersion](../../includes/ssnoversion-md.md)]. You must be a system administrator to change this policy.

Copilot uses AI. Check for mistakes.
@ktoliver
Copy link
Contributor

@rwestMSFT

Can you review the proposed changes?

IMPORTANT: When the changes are ready for publication, adding a #sign-off comment is the best way to signal that the PR is ready for the review team to merge.

#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team

@prmerger-automator prmerger-automator bot added the aq-pr-triaged tracking label for the PR review team label Oct 30, 2025
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