Merge pull request #35925 from MicrosoftDocs/main

Auto Publish – main to live - 2025-11-24 23:30 UTC

Author: learn-build-service-prod[bot]

azure-sql/database/auditing-microsoft-support-operations.md

@@ -5,10 +5,10 @@ description: How to use Auditing to audit Microsoft support operations.
 author: sravanisaluru
 ms.author: srsaluru
 ms.reviewer: mathoma, vanto
-ms.date: 09/18/2025
+ms.date: 11/24/2025
 ms.service: azure-sql-database
 ms.subservice: security
-ms.topic: conceptual
+ms.topic: concept-article
 ---
 # Auditing Microsoft support operations
 
@@ -37,6 +37,14 @@ AzureDiagnostics
 
 You have the option of choosing a different storage destination for this auditing log, or use the same auditing configuration for your server.
 
+> [!NOTE]
+> DevOps audit logs stored in Azure Storage may contain sensitive operational details. If a malicious actor within your environment accesses these logs, they could gain insights into system operations, which may lead to unauthorized access or data breaches.
+>
+> **Customer responsibility -** Secure these logs by:
+> - Restricting access to authorized personnel only
+> - Applying strong Azure role-based access control (RBAC) and network controls
+> - Monitoring and auditing storage access regularly
+
 ## Related content
 
 - [Auditing for Azure SQL Database and Azure Synapse Analytics](auditing-overview.md)

azure-sql/managed-instance/service-tiers-next-gen-general-purpose-use.md

@@ -4,7 +4,7 @@ description: Learn how to use the Next-gen General Purpose service tier in Azure
 author: urosmil
 ms.author: urmilano
 ms.reviewer: wiassaf, mathoma
-ms.date: 11/18/2025
+ms.date: 11/21/2025
 ms.service: azure-sql-managed-instance
 ms.subservice: service-overview
 ms.topic: how-to
@@ -33,9 +33,6 @@ To upgrade an existing instance to the Next-gen General Purpose service tier in
 1. After *Next-gen General Purpose* is enabled, you can use the sliders to modify the IOPS and memory for the instance. Review the *Cost per IOPS* and *Cost per GB* in the **Estimated costs per month** box. 
 1. Select **Apply** to save your changes. 
 
-> [!NOTE]
-> For instances inside of a failover group, changing the service tier to or from the Next-gen General Purpose tier isn't supported. You must first delete the failover group before modifying either replica, and then re-create the failover group after the change takes effect.
-
 ## New instances 
 
 You can use the Next-gen General Purpose tier upgrade for new instances when you deploy them in the Azure portal.  To do so, follow these steps:

docs/relational-databases/system-catalog-views/sys-indexes-transact-sql.md

@@ -3,7 +3,7 @@ title: "sys.indexes (Transact-SQL)"
 description: "The sys.indexes catalog view contains a row per index or heap of a tabular object, such as a table, view, or table-valued function."
 author: rwestMSFT
 ms.author: randolphwest
-ms.date: 08/21/2025
+ms.date: 11/24/2025
 ms.service: sql
 ms.subservice: system-objects
 ms.topic: "reference"
@@ -35,11 +35,11 @@ Contains a row per index or heap of a tabular object, such as a table, view, or
 | `type_desc` | **nvarchar(60)** | Description of index type:<br /><br />- HEAP<br />- CLUSTERED<br />- NONCLUSTERED<br />- XML<br />- SPATIAL<br />- CLUSTERED COLUMNSTORE <sup>2</sup><br />- NONCLUSTERED COLUMNSTORE <sup>1</sup><br />- NONCLUSTERED HASH <sup>2, 8</sup><br />- JSON <sup>5</sup> |
 | `is_unique` | **bit** | 1 = Index is unique.<br />0 = Index isn't unique.<br /><br />Always 0 for clustered columnstore indexes. |
 | `data_space_id` | **int** | ID of the data space for this index. Data space is either a filegroup or partition scheme.<br /><br />0 = object_id is a table-valued function or in-memory index. |
-| `ignore_dup_key` | **bit** | 1 = IGNORE_DUP_KEY is OFF.<br />0 = IGNORE_DUP_KEY is OFF. |
+| `ignore_dup_key` | **bit** | 1 = IGNORE_DUP_KEY is ON.<br />0 = IGNORE_DUP_KEY is OFF. |
 | `is_primary_key` | **bit** | 1 = Index is part of a PRIMARY KEY constraint.<br /><br />Always 0 for clustered columnstore indexes. |
 | `is_unique_constraint` | **bit** | 1 = Index is part of a UNIQUE constraint.<br /><br />Always 0 for clustered columnstore indexes. |
 | `fill_factor` | **tinyint** | > 0 = FILLFACTOR percentage used when the index was created or rebuilt.<br />0 = Default value<br /><br />Always 0 for clustered columnstore indexes. |
-| `is_padded` | **bit** | 1 = PADINDEX is OFF.<br />0 = PADINDEX is OFF.<br /><br />Always 0 for clustered columnstore indexes. |
+| `is_padded` | **bit** | 1 = PADINDEX is ON.<br />0 = PADINDEX is OFF.<br /><br />Always 0 for clustered columnstore indexes. |
 | `is_disabled` | **bit** | 1 = Index is disabled.<br />0 = Index isn't disabled. |
 | `is_hypothetical` | **bit** | 1 = Index is hypothetical and can't be used directly as a data access path. Hypothetical indexes hold column-level statistics.<br /><br />0 = Index isn't hypothetical. |
 | `allow_row_locks` | **bit** | 1 = Index allows row locks.<br />0 = Index doesn't allow row locks.<br /><br />Always 0 for clustered columnstore indexes. |