Align some MSSQL features names of version 2016,2017,2022 with MSSQL 2025

[rferraton]

Align some MSSQL features names of version 2016,2017,2022 with MSSQL 2025 for more clear features evolutions tracking

[rferraton]

@microsoft-github-policy-service agree company="Architecture & Performance"

[prmerger-automator]

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

[learn-build-service-prod]

Learn Build status updates of commit ed513b1:

✅ Validation status: passed

File	Status	Preview URL	Details
docs/sql-server/editions-and-components-of-sql-server-2016.md	✅Succeeded
docs/sql-server/editions-and-components-of-sql-server-2017.md	✅Succeeded
docs/sql-server/editions-and-components-of-sql-server-2019.md	✅Succeeded
docs/sql-server/editions-and-components-of-sql-server-2022.md	✅Succeeded

For more details, please refer to the build report.

[Copilot]

Pull Request Overview

This PR standardizes feature naming across SQL Server documentation versions (2016, 2017, 2019, 2022) to align with SQL Server 2025 terminology, improving consistency for tracking feature evolution.

Key changes:

• Removed "Intelligent Database" prefix from query optimization features
• Standardized tool and feature descriptions (sqlcmd, Service Broker, parallel index operations, Query Store)

Reviewed Changes

Copilot reviewed 4 out of 4 changed files in this pull request and generated no comments.

File	Description
editions-and-components-of-sql-server-2022.md	Updated 18 feature names removing "Intelligent Database" prefix and standardizing descriptions
editions-and-components-of-sql-server-2019.md	Aligned 7 feature names with 2025 conventions
editions-and-components-of-sql-server-2017.md	Updated 3 feature names for consistency
editions-and-components-of-sql-server-2016.md	Updated 3 feature names to match 2025 terminology

---

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

[ttorble]

@MikeRayMSFT @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

[rwestMSFT]

@rferraton Thanks, this is something I had already planned to do. We'll take this into an internal PR and close this one. You'll still get credit for the PR.