Include file cleanup and article refresh

rwestMSFT · rwestMSFT · commit 9b6919b0fbab · 2025-12-15T10:21:46.000-07:00
diff --git a/docs/linux/sql-server-linux-availability-group-cross-platform.md b/docs/linux/sql-server-linux-availability-group-cross-platform.md
@@ -4,26 +4,26 @@ description: Learn how to create a SQL Server Always On Availability Group (AG)
 author: rwestMSFT
 ms.author: randolphwest
 ms.reviewer: vanto
-ms.date: 07/03/2025
+ms.date: 12/15/2025
 ms.service: sql
 ms.subservice: linux
 ms.topic: how-to
-monikerRange: ">=sql-server-2017"
 ms.custom:
   - linux-related-content
   - sfi-image-nochange
+monikerRange: ">=sql-server-2017"
 ---
 # Configure SQL Server Always On availability group on Windows and Linux (cross-platform)
 
-[!INCLUDE [tsql-appliesto-sslinux-only](../includes/applies-to-version/sqlserver2017.md)]
+[!INCLUDE [sqlserver2017](../includes/applies-to-version/sqlserver2017.md)]
 
 This article explains the steps to create an Always On availability group (AG) with one replica on a Windows server and the other replica on a Linux server.
 
 > [!IMPORTANT]  
 > [!INCLUDE [ssnoversion-md](../includes/ssnoversion-md.md)] cross-platform availability groups, which include heterogeneous replicas with complete high-availability and disaster recovery support, is available with DH2i DxEnterprise. For more information, see [SQL Server Availability Groups with Mixed Operating Systems](https://support.dh2i.com/docs/guides/dxenterprise/sql_server/mssql-ag-mixed-os-qsg).
->  
+>
 > View the following video to find out about cross-platform availability groups with DH2i.
->  
+>
 > [!VIDEO https://learn-video.azurefd.net/vod/player?show=data-exposed&ep=get-started-with-sql-server-ags-across-windows-linux-and-container-replicas]
 
 This configuration is cross-platform because the replicas are on different operating systems. Use this configuration for migration from one platform to the other or disaster recovery (DR). This configuration doesn't support high availability.
@@ -190,9 +190,9 @@ For the scripts in this article, angle brackets `<` and `>` identify values that
 
    > [!NOTE]  
    > When the Windows instance of SQL Server uses different paths for data and log files, automatic seeding fails to the Linux instance of SQL Server, because these paths don't exist on the secondary replica. To use the following script for a cross-platform AG, the database requires the same path for the data and log files on the Windows server. Alternatively you can update the script to set `SEEDING_MODE = MANUAL` and then back up and restore the database with `NORECOVERY` to seed the database.  
-   >  
+   >
    > This behavior applies to Azure Marketplace images.
-   >  
+   >
    > For more information about automatic seeding, see [Automatic Seeding - Disk Layout](../database-engine/availability-groups/windows/automatic-seeding-secondary-replicas.md#disklayout).
 
    Before you run the script, update the values for your AGs.
diff --git a/docs/sql-server/applies-to-includes.md b/docs/sql-server/applies-to-includes.md
@@ -4,7 +4,7 @@ description: Explanation of SQL Server includes files for versioning and applies
 author: MashaMSFT
 ms.author: mathoma
 ms.reviewer: randolphwest
-ms.date: 05/26/2025
+ms.date: 12/15/2025
 ms.service: sql
 ms.subservice: release-landing
 ms.topic: article
@@ -18,7 +18,7 @@ This article is meant to be used as a reference point for just the first two typ
 
 ## SQL Server version include files
 
-SQL Content writers frequently need to include the name of the product and version of SQL Server. This way, if something changes in the name, the include file is updated instead of manually updating the value in every single article. These include files are used as placeholders for product names but haven't been consistently used in all SQL documentation. SQL Server vNext refers to a future release of SQL that doesn't yet have a version number and is the exception to this.
+SQL Content writers frequently need to include the name of the product and version of SQL Server. This way, if something changes in the name, the include file is updated instead of manually updating the value in every single article. These include files are used as placeholders for product names but aren't consistently used in all SQL documentation. SQL Server vNext refers to a future release of SQL Server that doesn't yet have a version number, and is the exception to this rule.
 
 | SQL Server version | File name | Markdown example | Text |
 | --- | --- | --- | --- |
@@ -34,7 +34,7 @@ SQL Content writers frequently need to include the name of the product and versi
 | SQL Server 2017 | sssql17-md.md | `[!INCLUDE [sssql17-md](../includes/sssql17-md.md)]` | [!INCLUDE [sssql17-md](../includes/sssql17-md.md)] |
 | SQL Server 2019 | sssql19-md.md | `[!INCLUDE [sssql19-md](../includes/sssql19-md.md)]` | [!INCLUDE [sssql19-md](../includes/sssql19-md.md)] |
 | SQL Server 2022 | sssql22-md.md | `[!INCLUDE [sssql22-md](../includes/sssql22-md.md)]` | [!INCLUDE [sssql22-md](../includes/sssql22-md.md)] |
-| SQL Server 2025 | sssql22-md.md | `[!INCLUDE [sssql25-md](../includes/sssql25-md.md)]` | [!INCLUDE [sssql25-md](../includes/sssql25-md.md)] |
+| SQL Server 2025 | sssql25-md.md | `[!INCLUDE [sssql25-md](../includes/sssql25-md.md)]` | [!INCLUDE [sssql25-md](../includes/sssql25-md.md)] |
 | SQL Server vNext | sssql22-md.md | `[!INCLUDE [sssql22-md](../includes/sssql22-md.md)]` | [!INCLUDE [sssql22-md](../includes/sssql22-md.md)] |
 
 ## SQL Server applies-to (non-version-specific)
@@ -53,8 +53,6 @@ These applies-to include files specify which versions of SQL the documentation a
 | File name | Markdown example | Image |
 | --- | --- | --- |
 | applies-to-version/asa-pdw.md | `[!INCLUDE [applies-to-version/asa-pdw.md](../includes/applies-to-version/asa-pdw.md)]` | [!INCLUDE [applies-to-version/asa-pdw.md](../includes/applies-to-version/asa-pdw.md)] |
-| tsql-appliesto-ss2008-xxxx-xxxx-xxx-md.md | `[!INCLUDE [tsql-appliesto-ss2008-xxxx-xxxx-xxx-md.md](../includes/applies-to-version/sqlserver.md)]` | [!INCLUDE [tsql-appliesto-ss2008-xxxx-xxxx-xxx-md.md](../includes/applies-to-version/sqlserver.md)] |
-| tsql-appliesto-ss2017-xxxx-xxxx-xxx-md.md | `[!INCLUDE [tsql-appliesto-ss2017-xxxx-xxxx-xxx-md.md](../includes/applies-to-version/sqlserver2017.md)]` | [!INCLUDE [tsql-appliesto-ss2017-xxxx-xxxx-xxx-md.md](../includes/applies-to-version/sqlserver2017.md)] |
 
 ## Related content
 
diff --git a/docs/sql-server/sql-server-docs-contribute.md b/docs/sql-server/sql-server-docs-contribute.md
@@ -4,7 +4,7 @@ description: "How to contribute to SQL Server Documentation"
 author: MikeRayMSFT
 ms.author: mikeray
 ms.reviewer: randolphwest
-ms.date: 05/26/2025
+ms.date: 12/15/2025
 ms.service: sql
 ms.subservice: release-landing
 ms.topic: how-to
@@ -39,10 +39,10 @@ The following steps summarize the process:
 1. On the page you have feedback about, select the **Pencil** icon at the top right.
 1. On the next page, select the **Pencil** icon at the top right. If this icon doesn't appear, you might need to sign in to your GitHub account first.
 1. On the next page, in the **Edit file** text window, make your edits directly to the text you want to change.
-    If you need help with formatting the new or changed text, see the [Markdown Cheatsheet](https://github.com/adam-p/markdown-here/wiki/Markdown-Cheatsheet).
+   If you need help with formatting the new or changed text, see the [Markdown Cheatsheet](https://github.com/adam-p/markdown-here/wiki/Markdown-Cheatsheet).
 1. After you make your edits, under **Commit changes**:
-    1. In the first text box, enter a brief description of the change you make.
-    1. In the **Add an optional extended description** box, provide a brief explanation of your change.
+   1. In the first text box, enter a brief description of the change you make.
+   1. In the **Add an optional extended description** box, provide a brief explanation of your change.
 1. Select **Propose file change**.
 1. On the **Comparing changes** page, select **Create pull request**.
 1. On the **Open a pull request** page, select **Create pull request**.
@@ -111,8 +111,7 @@ To find the correct applies-to include file for your article, use the following
 - For a list of commonly used includes, see [SQL Server include files for versioning and applies-to](applies-to-includes.md).
 - Look at other articles that cover the same feature or a related task. If you edit that article, you can copy the Markdown for the applies-to include link (you can cancel the edit without submitting it).
 - Search the [docs/includes](https://github.com/MicrosoftDocs/sql-docs/tree/live/docs/includes) directory for files containing the text `applies-to`. You can use the **Find** button in GitHub to quickly filter. Select the file to see how it renders.
-- Pay attention to the naming convention. If the name contains multiple `x` characters in the string, they're usually placeholders indicating the lack of support for a service. For example, `appliesto-xx-xxxx-asdw-xxx-md.md` indicates support for only Azure Synapse Analytics, because only `asdw` is spelled out, whereas the other fields are filled with the `x` character.
-- Some includes specify a version number, such as `tsql-appliesto-ss2017-xxxx-xxxx-xxx-md.md`. Only use these include files when you know the feature was introduced with a specific version of SQL Server.
+- Some includes specify a version number, such as `sql-asdbmi-asa-pdw.md`. Only use this kind of include file when you know the feature was introduced with a specific version of SQL Server.
 
 ## Contributor resources
 
@@ -123,7 +122,7 @@ To find the correct applies-to include file for your article, use the following
 > [!TIP]  
 > If you have product feedback rather than documentation feedback, [provide feedback](https://feedback.azure.com/forums/908035-sql-server).
 
-## Related content
+## Next step
 
 Explore the [sql-docs repository](https://github.com/MicrosoftDocs/sql-docs) on GitHub.
 
diff --git a/docs/t-sql/database-console-commands/dbcc-traceon-trace-flags-transact-sql.md b/docs/t-sql/database-console-commands/dbcc-traceon-trace-flags-transact-sql.md
@@ -24,7 +24,7 @@ dev_langs:
 
 # Set trace flags with DBCC TRACEON (Transact-SQL)
 
-[!INCLUDE [tsql-appliesto-ss-asdmi-md](../../includes/applies-to-version/sql-asdbmi.md)]
+[!INCLUDE [sql-asdbmi](../../includes/applies-to-version/sql-asdbmi.md)]
 
 Trace flags are used to set specific server characteristics or to alter a particular behavior. For example, trace flag 3226 is a commonly used startup trace flag that suppresses successful backup messages in the error log. Trace flags might be used to diagnose or mitigate performance issues, but they might also be recommended by Microsoft to address behavior that is negatively affecting a specific workload. Conversely, Microsoft might recommend that you remove a trace flag if it causes or contributes to a problem affecting your workload.
 
diff --git a/docs/t-sql/statements/drop-partition-scheme-transact-sql.md b/docs/t-sql/statements/drop-partition-scheme-transact-sql.md
@@ -1,9 +1,10 @@
 ---
 title: "DROP PARTITION SCHEME (Transact-SQL)"
-description: DROP PARTITION SCHEME (Transact-SQL)
+description: DROP PARTITION SCHEME removes a partition scheme from the current database.
 author: WilliamDAssafMSFT
 ms.author: wiassaf
-ms.date: "03/06/2017"
+ms.reviewer: randolphwest
+ms.date: 12/15/2025
 ms.service: sql
 ms.subservice: t-sql
 ms.topic: reference
@@ -20,51 +21,57 @@ dev_langs:
   - "TSQL"
 ---
 # DROP PARTITION SCHEME (Transact-SQL)
-[!INCLUDE[tsql-appliesto-ss2008-asdb-xxxx-xxx-md](../../includes/applies-to-version/sql-asdbmi.md)]
-
-  Removes a partition scheme from the current database. Partition schemes are created by using [CREATE PARTITION SCHEME](../../t-sql/statements/create-partition-scheme-transact-sql.md) and modified by using [ALTER PARTITION SCHEME](../../t-sql/statements/alter-partition-scheme-transact-sql.md).  
-  
- :::image type="icon" source="../../includes/media/topic-link-icon.svg" border="false"::: [Transact-SQL syntax conventions](../../t-sql/language-elements/transact-sql-syntax-conventions-transact-sql.md)  
-  
-## Syntax  
-  
+
+[!INCLUDE [sql-asdbmi](../../includes/applies-to-version/sql-asdbmi.md)]
+
+Removes a partition scheme from the current database. Partition schemes are created by using [CREATE PARTITION SCHEME](create-partition-scheme-transact-sql.md) and modified by using [ALTER PARTITION SCHEME](alter-partition-scheme-transact-sql.md).
+
+:::image type="icon" source="../../includes/media/topic-link-icon.svg" border="false"::: [Transact-SQL syntax conventions](../../t-sql/language-elements/transact-sql-syntax-conventions-transact-sql.md)
+
+## Syntax
+
 ```syntaxsql
-DROP PARTITION SCHEME partition_scheme_name [ ; ]  
-```  
-  
+DROP PARTITION SCHEME partition_scheme_name
+[ ; ]
+```
+
 ## Arguments
- *partition_scheme_name*  
- Is the name of the partition scheme to be dropped.  
-  
-## Remarks  
- A partition scheme can be dropped only if there are no tables or indexes currently using the partition scheme. If there are tables or indexes using the partition scheme, DROP PARTITION SCHEME returns an error. DROP PARTITION SCHEME does not remove the filegroups themselves.  
-  
-## Permissions  
- The following permissions can be used to execute DROP PARTITION SCHEME:  
-  
--   ALTER ANY DATASPACE permission. This permission defaults to members of the **sysadmin** fixed server role and the **db_owner** and **db_ddladmin** fixed database roles.  
-  
--   CONTROL or ALTER permission on the database in which the partition scheme was created.  
-  
--   CONTROL SERVER or ALTER ANY DATABASE permission on the server of the database in which the partition scheme was created.  
-  
-## Examples  
- The following example drops the partition scheme `myRangePS1` from the current database:  
-  
-```sql  
-DROP PARTITION SCHEME myRangePS1;  
-```  
-  
-## See Also  
- [CREATE PARTITION SCHEME &#40;Transact-SQL&#41;](../../t-sql/statements/create-partition-scheme-transact-sql.md)   
- [ALTER PARTITION SCHEME &#40;Transact-SQL&#41;](../../t-sql/statements/alter-partition-scheme-transact-sql.md)   
- [sys.partition_schemes &#40;Transact-SQL&#41;](../../relational-databases/system-catalog-views/sys-partition-schemes-transact-sql.md)   
- [EVENTDATA &#40;Transact-SQL&#41;](../../t-sql/functions/eventdata-transact-sql.md)   
- [sys.data_spaces &#40;Transact-SQL&#41;](../../relational-databases/system-catalog-views/sys-data-spaces-transact-sql.md)   
- [sys.destination_data_spaces &#40;Transact-SQL&#41;](../../relational-databases/system-catalog-views/sys-destination-data-spaces-transact-sql.md)   
- [sys.partitions &#40;Transact-SQL&#41;](../../relational-databases/system-catalog-views/sys-partitions-transact-sql.md)   
- [sys.tables &#40;Transact-SQL&#41;](../../relational-databases/system-catalog-views/sys-tables-transact-sql.md)   
- [sys.indexes &#40;Transact-SQL&#41;](../../relational-databases/system-catalog-views/sys-indexes-transact-sql.md)   
- [sys.index_columns &#40;Transact-SQL&#41;](../../relational-databases/system-catalog-views/sys-index-columns-transact-sql.md)  
-  
-  
+
+#### *partition_scheme_name*
+
+The name of the partition scheme to be dropped.
+
+## Remarks
+
+A partition scheme can be dropped only if there are no tables or indexes currently using the partition scheme. If there are tables or indexes using the partition scheme, `DROP PARTITION SCHEME` returns an error. `DROP PARTITION SCHEME` doesn't remove the filegroups themselves.
+
+## Permissions
+
+The following permissions can be used to execute `DROP PARTITION SCHEME`:
+
+- `ALTER ANY DATASPACE` permission. This permission defaults to members of the **sysadmin** fixed server role and the **db_owner** and **db_ddladmin** fixed database roles.
+
+- `CONTROL` or `ALTER` permission on the database in which the partition scheme was created.
+
+- `CONTROL SERVER` or `ALTER ANY DATABASE` permission on the server of the database in which the partition scheme was created.
+
+## Examples
+
+The following example drops the partition scheme `myRangePS1` from the current database:
+
+```sql
+DROP PARTITION SCHEME myRangePS1;
+```
+
+## Related content
+
+- [CREATE PARTITION SCHEME (Transact-SQL)](create-partition-scheme-transact-sql.md)
+- [ALTER PARTITION SCHEME (Transact-SQL)](alter-partition-scheme-transact-sql.md)
+- [sys.partition_schemes (Transact-SQL)](../../relational-databases/system-catalog-views/sys-partition-schemes-transact-sql.md)
+- [EVENTDATA (Transact-SQL)](../functions/eventdata-transact-sql.md)
+- [sys.data_spaces (Transact-SQL)](../../relational-databases/system-catalog-views/sys-data-spaces-transact-sql.md)
+- [sys.destination_data_spaces (Transact-SQL)](../../relational-databases/system-catalog-views/sys-destination-data-spaces-transact-sql.md)
+- [sys.partitions (Transact-SQL)](../../relational-databases/system-catalog-views/sys-partitions-transact-sql.md)
+- [sys.tables (Transact-SQL)](../../relational-databases/system-catalog-views/sys-tables-transact-sql.md)
+- [sys.indexes (Transact-SQL)](../../relational-databases/system-catalog-views/sys-indexes-transact-sql.md)
+- [sys.index_columns (Transact-SQL)](../../relational-databases/system-catalog-views/sys-index-columns-transact-sql.md)
diff --git a/docs/t-sql/statements/drop-server-role-transact-sql.md b/docs/t-sql/statements/drop-server-role-transact-sql.md
