Merge pull request #31731 from MicrosoftDocs/main

9/03/2024 AM Publish

Author: Albertyang0

azure-sql/database/high-availability-sla-local-zone-redundancy.md

@@ -185,7 +185,7 @@ Consider the following when configuring your Premium or Business Critical databa
 
 It's possible to configure zone-redundancy for databases in the Hyperscale service tier. To learn more, review [Create zone-redundant Hyperscale database](hyperscale-create-zone-redundant-database.md). 
 
-Enabling this configuration ensures zone-level resiliency through replication across Availability Zones for all Hyperscale layers. By selecting zone-redundancy, you can make your Hyperscale databases resilient to a much larger set of failures, including catastrophic datacenter outages, without any changes to the application logic. All Azure regions that have [Availability Zones](/azure/availability-zones/az-overview#azure-regions-with-availability-zones) support zone redundant Hyperscale database.
+Enabling this configuration ensures zone-level resiliency through replication across Availability Zones for all Hyperscale layers. By selecting zone-redundancy, you can make your Hyperscale databases resilient to a much larger set of failures, including catastrophic datacenter outages, without any changes to the application logic. All Azure regions that have [Availability Zones](/azure/availability-zones/az-overview#azure-regions-with-availability-zones) support zone redundant Hyperscale database. Zone redundancy support for Hyperscale PRMS and MOPRMS hardware is available in regions listed [here](service-tiers-sql-database-vcore.md#hyperscale-premium-series-availability).
 
 Zone-redundant availability is supported in both Hyperscale standalone databases and Hyperscale elastic pools. For more information, see [Hyperscale elastic pools](hyperscale-elastic-pool-overview.md).
 

azure-sql/database/resource-limits-vcore-elastic-pools.md

@@ -603,7 +603,7 @@ The following table covers these SLOs: `HS_Gen5_4`, `HS_Gen5_6`, `HS_Gen5_8`, `H
 | Max concurrent sessions | 30,000 | 30,000 | 30,000 | 30,000 | 30,000 | 30,000 |
 | Min/max elastic pool vCore choices per database | 0, 0.25, 0.5, 1, 2, 4 | 0, 0.25, 0.5, 1, 2, 4, 6 | 0, 0.25, 0.5, 1, 2, 4, 6, 8 | 0, 0.25, 0.5, 1, 2, 4, 6, 8, 10 | 0, 0.25, 0.5, 1, 2, 4, 6, 8, 10, 12 | 0, 0.25, 0.5, 1, 2, 4, 6, 8, 10, 12, 14 |
 | Secondary pool replicas | 0-4 | 0-4 | 0-4 | 0-4 | 0-4 | 0-4 |
-| Multi-AZ | Not supported | Not supported | Not supported | Not supported | Not supported | Not supported |
+| Multi-AZ | [Yes](high-availability-sla-local-zone-redundancy.md#hyperscale-service-tier-zone-redundant-availability) | [Yes](high-availability-sla-local-zone-redundancy.md#hyperscale-service-tier-zone-redundant-availability) | [Yes](high-availability-sla-local-zone-redundancy.md#hyperscale-service-tier-zone-redundant-availability) | [Yes](high-availability-sla-local-zone-redundancy.md#hyperscale-service-tier-zone-redundant-availability) | [Yes](high-availability-sla-local-zone-redundancy.md#hyperscale-service-tier-zone-redundant-availability) | [Yes](high-availability-sla-local-zone-redundancy.md#hyperscale-service-tier-zone-redundant-availability) |
 | Read Scale-out | Yes | Yes | Yes | Yes | Yes | Yes |
 
 <sup>1</sup> See [Resource management in dense elastic pools](elastic-pool-resource-management.md) for additional considerations.
@@ -644,7 +644,7 @@ The following table covers these SLOs: `HS_Gen5_16`, `HS_Gen5_18`, `HS_Gen5_20`,
 | Max concurrent sessions | 30,000 | 30,000 | 30,000 | 30,000 | 30,000 | 30,000 | 30,000 |
 | Min/max elastic pool vCore choices per database | 0, 0.25, 0.5, 1, 2, 4, 6, 8, 10, 12, 14, 16 | 0, 0.25, 0.5, 1, 2, 4, 6, 8, 10, 12, 14, 16, 18 | 0, 0.25, 0.5, 1, 2, 4, 6, 8, 10, 12, 14, 16, 18, 20 | 0, 0.25, 0.5, 1, 2, 4, 6, 8, 10, 12, 14, 16, 18, 20, 24 | 0, 0.25, 0.5, 1, 2, 4, 6, 8, 10, 12, 14, 16, 18, 20, 24, 32 | 0, 0.25, 0.5, 1, 2, 4, 6, 8, 10, 12, 14, 16, 18, 20, 24, 32, 40 | 0, 0.25, 0.5, 1, 2, 4, 6, 8, 10, 12, 14, 16, 18, 20, 24, 32, 40, 80 |
 | Secondary replicas | 0-4 | 0-4 | 0-4 | 0-4 | 0-4 | 0-4 | 0-4 |
-| Multi-AZ | Not supported | Not supported | Not supported | Not supported | Not supported | Not supported | Not supported |
+| Multi-AZ | [Yes](high-availability-sla-local-zone-redundancy.md#hyperscale-service-tier-zone-redundant-availability) | [Yes](high-availability-sla-local-zone-redundancy.md#hyperscale-service-tier-zone-redundant-availability) | [Yes](high-availability-sla-local-zone-redundancy.md#hyperscale-service-tier-zone-redundant-availability) | [Yes](high-availability-sla-local-zone-redundancy.md#hyperscale-service-tier-zone-redundant-availability) | [Yes](high-availability-sla-local-zone-redundancy.md#hyperscale-service-tier-zone-redundant-availability) | [Yes](high-availability-sla-local-zone-redundancy.md#hyperscale-service-tier-zone-redundant-availability) | [Yes](high-availability-sla-local-zone-redundancy.md#hyperscale-service-tier-zone-redundant-availability) |
 | Read Scale-out | Yes | Yes | Yes | Yes | Yes | Yes | Yes |
 
 <sup>1</sup> See [Resource management in dense elastic pools](elastic-pool-resource-management.md) for additional considerations.
@@ -687,7 +687,7 @@ The following table covers these SLOs: `HS_PRMS_4`, `HS_PRMS_6`, `HS_PRMS_8`, `H
 | Max concurrent sessions | 30,000 | 30,000 | 30,000 | 30,000 | 30,000 | 30,000 |
 | Min/max elastic pool vCore choices per database | 0, 0.25, 0.5, 1, 2, 4 | 0, 0.25, 0.5, 1, 2, 4, 6 | 0, 0.25, 0.5, 1, 2, 4, 6, 8 | 0, 0.25, 0.5, 1, 2, 4, 6, 8, 10 | 0, 0.25, 0.5, 1, 2, 4, 6, 8, 10, 12 | 0, 0.25, 0.5, 1, 2, 4, 6, 8, 10, 12, 14 |
 | Secondary pool replicas | 0-4 | 0-4 | 0-4 | 0-4 | 0-4 | 0-4 |
-| Multi-AZ | Not supported | Not supported | Not supported | Not supported | Not supported | Not supported |
+| Multi-AZ | [Yes](high-availability-sla-local-zone-redundancy.md#hyperscale-service-tier-zone-redundant-availability) | [Yes](high-availability-sla-local-zone-redundancy.md#hyperscale-service-tier-zone-redundant-availability) | [Yes](high-availability-sla-local-zone-redundancy.md#hyperscale-service-tier-zone-redundant-availability) | [Yes](high-availability-sla-local-zone-redundancy.md#hyperscale-service-tier-zone-redundant-availability) | [Yes](high-availability-sla-local-zone-redundancy.md#hyperscale-service-tier-zone-redundant-availability) | [Yes](high-availability-sla-local-zone-redundancy.md#hyperscale-service-tier-zone-redundant-availability) |
 | Read Scale-out | Yes | Yes | Yes | Yes | Yes | Yes |
 
 <sup>1</sup> See [Resource management in dense elastic pools](elastic-pool-resource-management.md) for additional considerations.
@@ -728,7 +728,7 @@ The following table covers these SLOs: `HS_PRMS_16`, `HS_PRMS_18`, `HS_PRMS_20`,
 | Max concurrent sessions | 30,000 | 30,000 | 30,000 | 30,000 | 30,000 | 30,000 | 
 | Min/max elastic pool vCore choices per database | 0, 0.25, 0.5, 1, 2, 4, 6, 8, 10, 12, 14, 16 | 0, 0.25, 0.5, 1, 2, 4, 6, 8, 10, 12, 14, 16, 18 | 0, 0.25, 0.5, 1, 2, 4, 6, 8, 10, 12, 14, 16, 18, 20 | 0, 0.25, 0.5, 1, 2, 4, 6, 8, 10, 12, 14, 16, 18, 20, 24 | 0, 0.25, 0.5, 1, 2, 4, 6, 8, 10, 12, 14, 16, 18, 20, 24, 32 | 0, 0.25, 0.5, 1, 2, 4, 6, 8, 10, 12, 14, 16, 18, 20, 24, 32, 40 |
 | Secondary replicas | 0-4 | 0-4 | 0-4 | 0-4 | 0-4 | 0-4 | 
-| Multi-AZ | Not supported | Not supported | Not supported | Not supported | Not supported | Not supported | 
+| Multi-AZ | [Yes](high-availability-sla-local-zone-redundancy.md#hyperscale-service-tier-zone-redundant-availability) | [Yes](high-availability-sla-local-zone-redundancy.md#hyperscale-service-tier-zone-redundant-availability) | [Yes](high-availability-sla-local-zone-redundancy.md#hyperscale-service-tier-zone-redundant-availability) | [Yes](high-availability-sla-local-zone-redundancy.md#hyperscale-service-tier-zone-redundant-availability) | [Yes](high-availability-sla-local-zone-redundancy.md#hyperscale-service-tier-zone-redundant-availability) | [Yes](high-availability-sla-local-zone-redundancy.md#hyperscale-service-tier-zone-redundant-availability) | 
 | Read Scale-out | Yes | Yes | Yes | Yes | Yes | Yes | 
 
 <sup>1</sup> See [Resource management in dense elastic pools](elastic-pool-resource-management.md) for additional considerations.
@@ -769,7 +769,7 @@ The following table covers these SLOs: `HS_PRMS_64`, `HS_PRMS_80`, `HS_PRMS_128`
 | Max concurrent sessions | 30,000 | 30,000 | 30,000 | 
 | Min/max elastic pool vCore choices per database | 0, 0.25, 0.5, 1, 2, 4, 6, 8, 10, 12, 14, 16, 18, 20, 24, 32, 40, 64 | 0, 0.25, 0.5, 1, 2, 4, 6, 8, 10, 12, 14, 16, 18, 20, 24, 32, 40, 80 | 0, 0.25, 0.5, 1, 2, 4, 6, 8, 10, 12, 14, 16, 18, 20, 24, 32, 40, 64, 80, 128 |
 | Secondary replicas | 0-4 | 0-4 | 0-4 | 
-| Multi-AZ | Not supported | Not supported | Not supported |  
+| Multi-AZ | [Yes](high-availability-sla-local-zone-redundancy.md#hyperscale-service-tier-zone-redundant-availability) | [Yes](high-availability-sla-local-zone-redundancy.md#hyperscale-service-tier-zone-redundant-availability) | [Yes](high-availability-sla-local-zone-redundancy.md#hyperscale-service-tier-zone-redundant-availability) |  
 | Read Scale-out | Yes | Yes | Yes |  
 
 <sup>1</sup> See [Resource management in dense elastic pools](elastic-pool-resource-management.md) for additional considerations.
@@ -812,7 +812,7 @@ The following table covers these SLOs: `HS_MOPRMS_4`, `HS_MOPRMS_6`, `HS_MOPRMS_
 | Max concurrent sessions | 30,000 | 30,000 | 30,000 | 30,000 | 30,000 | 30,000 |
 | Min/max elastic pool vCore choices per database | 0, 0.25, 0.5, 1, 2, 4 | 0, 0.25, 0.5, 1, 2, 4, 6 | 0, 0.25, 0.5, 1, 2, 4, 6, 8 | 0, 0.25, 0.5, 1, 2, 4, 6, 8, 10 | 0, 0.25, 0.5, 1, 2, 4, 6, 8, 10, 12 | 0, 0.25, 0.5, 1, 2, 4, 6, 8, 10, 12, 14 |
 | Secondary pool replicas | 0-4 | 0-4 | 0-4 | 0-4 | 0-4 | 0-4 |
-| Multi-AZ | Not supported | Not supported | Not supported | Not supported | Not supported | Not supported |
+| Multi-AZ | [Yes](high-availability-sla-local-zone-redundancy.md#hyperscale-service-tier-zone-redundant-availability) | [Yes](high-availability-sla-local-zone-redundancy.md#hyperscale-service-tier-zone-redundant-availability) | [Yes](high-availability-sla-local-zone-redundancy.md#hyperscale-service-tier-zone-redundant-availability) | [Yes](high-availability-sla-local-zone-redundancy.md#hyperscale-service-tier-zone-redundant-availability) | [Yes](high-availability-sla-local-zone-redundancy.md#hyperscale-service-tier-zone-redundant-availability) | [Yes](high-availability-sla-local-zone-redundancy.md#hyperscale-service-tier-zone-redundant-availability) |
 | Read Scale-out | Yes | Yes | Yes | Yes | Yes | Yes |
 
 <sup>1</sup> See [Resource management in dense elastic pools](elastic-pool-resource-management.md) for additional considerations.
@@ -853,7 +853,7 @@ The following table covers these SLOs: `HS_MOPRMS_16`, `HS_MOPRMS_18`, `HS_MOPRM
 | Max concurrent sessions | 30,000 | 30,000 | 30,000 | 30,000 | 30,000 | 30,000 | 
 | Min/max elastic pool vCore choices per database | 0, 0.25, 0.5, 1, 2, 4, 6, 8, 10, 12, 14, 16 | 0, 0.25, 0.5, 1, 2, 4, 6, 8, 10, 12, 14, 16, 18 | 0, 0.25, 0.5, 1, 2, 4, 6, 8, 10, 12, 14, 16, 18, 20 | 0, 0.25, 0.5, 1, 2, 4, 6, 8, 10, 12, 14, 16, 18, 20, 24 | 0, 0.25, 0.5, 1, 2, 4, 6, 8, 10, 12, 14, 16, 18, 20, 24, 32 | 0, 0.25, 0.5, 1, 2, 4, 6, 8, 10, 12, 14, 16, 18, 20, 24, 32, 40 |
 | Secondary replicas | 0-4 | 0-4 | 0-4 | 0-4 | 0-4 | 0-4 |
-| Multi-AZ | Not supported | Not supported | Not supported | Not supported | Not supported | Not supported |
+| Multi-AZ | [Yes](high-availability-sla-local-zone-redundancy.md#hyperscale-service-tier-zone-redundant-availability) | [Yes](high-availability-sla-local-zone-redundancy.md#hyperscale-service-tier-zone-redundant-availability) | [Yes](high-availability-sla-local-zone-redundancy.md#hyperscale-service-tier-zone-redundant-availability) | [Yes](high-availability-sla-local-zone-redundancy.md#hyperscale-service-tier-zone-redundant-availability) | [Yes](high-availability-sla-local-zone-redundancy.md#hyperscale-service-tier-zone-redundant-availability) | [Yes](high-availability-sla-local-zone-redundancy.md#hyperscale-service-tier-zone-redundant-availability) |
 | Read Scale-out | Yes | Yes | Yes | Yes | Yes | Yes |
 
 <sup>1</sup> See [Resource management in dense elastic pools](elastic-pool-resource-management.md) for additional considerations.
@@ -894,7 +894,7 @@ The following table covers these SLOs: `HS_MOPRMS_64` and `HS_MOPRMS_80`:
 | Max concurrent sessions | 30,000 | 30,000 | 
 | Min/max elastic pool vCore choices per database | 0, 0.25, 0.5, 1, 2, 4, 6, 8, 10, 12, 14, 16, 18, 20, 24, 32, 40, 64 | 0, 0.25, 0.5, 1, 2, 4, 6, 8, 10, 12, 14, 16, 18, 20, 24, 32, 40, 80 | 
 | Secondary replicas | 0-4 | 0-4 | 
-| Multi-AZ | Not supported | Not supported | 
+| Multi-AZ | [Yes](high-availability-sla-local-zone-redundancy.md#hyperscale-service-tier-zone-redundant-availability) | [Yes](high-availability-sla-local-zone-redundancy.md#hyperscale-service-tier-zone-redundant-availability) | 
 | Read Scale-out | Yes | Yes | 
 
 <sup>1</sup> See [Resource management in dense elastic pools](elastic-pool-resource-management.md) for additional considerations.

azure-sql/managed-instance/native-windows-principals.md

@@ -5,7 +5,7 @@ description: Learn about the new authentication metadata modes that allow you to
 author: sravanisaluru
 ms.author: srsaluru
 ms.reviewer: mathoma, vanto, wiassaf
-ms.date: 07/03/2024
+ms.date: 09/03/2024
 ms.service: azure-sql-managed-instance
 ms.subservice: security
 ms.topic: conceptual
@@ -21,6 +21,9 @@ When your environment is synchronized between Active Directory (AD) and Microsof
 
 The authentication for SQL Managed Instance and SQL Server is based on metadata that are tied to logins. For Windows authentication logins, the metadata is created when the login is created from the `CREATE LOGIN FROM WINDOWS` command. For Microsoft Entra logins, the metadata is created when the login is created from the `CREATE LOGIN FROM EXTERNAL PROVIDER` command. For SQL authentication logins, the metadata is created when the `CREATE LOGIN WITH PASSWORD` command is executed. The authentication process is tightly coupled with the metadata stored in SQL Managed Instance or SQL Server.
 
+For a video explaining native Windows principals, you can also refer to this Data Exposed episode.
+> [!VIDEO https://learn-video.azurefd.net/vod/player?show=data-exposed&ep=native-windows-principals-for-sql-managed-instance-data-exposed]
+
 > [!NOTE]
 > Using native Windows principals with **Windows** authentication metadata mode in SQL Managed Instance is currently in preview.
 

azure-sql/toc.yml

@@ -1388,6 +1388,8 @@
         href: database/always-encrypted-landing.yml
       - name: Auditing
         href: managed-instance/auditing-configure.md
+      - name: Native Windows principals
+        href: managed-instance/native-windows-principals.md
       - name: Secure public endpoints
         href: managed-instance/public-endpoint-overview.md
       - name: Server trust groups

docs/includes/sssql10-md.md

@@ -371,7 +371,7 @@ The July 2011 release of SSMA for Access adds improved error reporting during da
 
 The April 2011 release of SSMA for Access contains the following changes:
 
-* Added a single installable of "SSMA for Access", which supports [!INCLUDE [ssVersion2005](../../includes/ssversion2005-md.md)], [!INCLUDE [ssSQL10](../../includes/sssql10-md.md)], [!INCLUDE [ssSQL11](../../includes/sssql11-md.md)] and Azure SQL.
+* Added a single installable of "SSMA for Access", which supports [!INCLUDE [ssVersion2005](../../includes/ssversion2005-md.md)], [!INCLUDE [sql2008-md](../../includes/sql2008-md.md)], [!INCLUDE [ssSQL11](../../includes/sssql11-md.md)] and Azure SQL.
 * Added the ability to connect to [!INCLUDE [ssSQL11](../../includes/sssql11-md.md)].
 * Added SSMA for Access Console version support for backward compatibility. You can open the projects created by versions earlier to SSMA v5.0.
 * Added the ability to install SSMA v5.0 product side by side (SxS) with older versions of SSMA Product.

docs/ssma/access/what-s-new-in-ssma-for-access-accesstosql.md

@@ -395,7 +395,7 @@ The July 2011 release of SSMA for MySQL contains the following changes:
 
 The April 2011 release of SSMA for MySQL contains the following changes:
 
-- Single installable of SSMA for MySQL, which supports [!INCLUDE [ssVersion2005](../../includes/ssversion2005-md.md)], [!INCLUDE [ssSQL10](../../includes/sssql10-md.md)], [!INCLUDE [ssSQL11](../../includes/sssql11-md.md)] and Azure SQL.
+- Single installable of SSMA for MySQL, which supports [!INCLUDE [ssVersion2005](../../includes/ssversion2005-md.md)], [!INCLUDE [sql2008-md](../../includes/sql2008-md.md)], [!INCLUDE [ssSQL11](../../includes/sssql11-md.md)] and Azure SQL.
 - The ability to connect [!INCLUDE [ssSQL11](../../includes/sssql11-md.md)].
 - Enhanced client-side data migration engine, supporting parallel migration of data.
 - Improved data migration performance with Simple and Bulk logged recovery models.

docs/ssma/mysql/what-s-new-in-ssma-for-mysql-mysqltosql.md

@@ -515,7 +515,7 @@ The July 2011 release of SSMA for Oracle contains the following changes:
 
 The April 2011 release of SSMA for Oracle contains the following changes:
 
-* Consolidated "SSMA for Oracle" product, which supports [!INCLUDE [ssVersion2005](../../includes/ssversion2005-md.md)], [!INCLUDE [ssSQL10](../../includes/sssql10-md.md)] and [!INCLUDE [ssSQL11](../../includes/sssql11-md.md)].
+* Consolidated "SSMA for Oracle" product, which supports [!INCLUDE [ssVersion2005](../../includes/ssversion2005-md.md)], [!INCLUDE [sql2008-md](../../includes/sql2008-md.md)] and [!INCLUDE [ssSQL11](../../includes/sssql11-md.md)].
 * Added support for connecting and migrating to [!INCLUDE [ssSQL11](../../includes/sssql11-md.md)].
 * Enhanced client-side data migration engine, supporting parallel migration of data.
 * Improved data migration performance with `Simple` and `Bulk` logged recovery models.

docs/ssma/oracle/what-s-new-in-ssma-for-oracle-oracletosql.md

@@ -383,7 +383,7 @@ The July 2011 release of SSMA for Sybase provides improved error reporting durin
 
 The April 2011 release of SSMA for Sybase contains the following changes:
 
-* Consolidated "SSMA for Sybase" product, which supports [!INCLUDE [ssVersion2005](../../includes/ssversion2005-md.md)], [!INCLUDE [ssSQL10](../../includes/sssql10-md.md)], [!INCLUDE [ssSQL11](../../includes/ssSQL11-md.md)] and Azure SQL.
+* Consolidated "SSMA for Sybase" product, which supports [!INCLUDE [ssVersion2005](../../includes/ssversion2005-md.md)], [!INCLUDE [sql2008-md](../../includes/sql2008-md.md)], [!INCLUDE [ssSQL11](../../includes/ssSQL11-md.md)] and Azure SQL.
 * Added support for connecting and migrating to [!INCLUDE [ssSQL11](../../includes/sssql11-md.md)].
 * Added a new feature to convert and migrate Sybase databases to Azure SQL.
 * Enhanced client-side data migration engine, supporting parallel migration of data.
@@ -419,7 +419,7 @@ The June 2008 release of SSMA for Sybase contains the following changes:
   * Clustered constraints and indexes on data-only-locked.
   * Temporary tables created by `SELECT INTO`.
   * Constraints / Indexes for temporary tables.
-  * New [!INCLUDE [ssSQL10](../../includes/sssql10-md.md)] datetime types are supported.
+  * New [!INCLUDE [sql2008-md](../../includes/sql2008-md.md)] datetime types are supported.
   * Sybase 15.0 connectivity and data types support.
 
 ## May 2007

docs/ssma/sybase/what-s-new-in-ssma-for-sybase-sybasetosql.md

@@ -27,7 +27,7 @@ monikerRange: "=azuresqldb-current || =azure-sqldw-latest || >=sql-server-2016 |
 
 Specifies the language environment for the session. The session language determines the **datetime** formats and system messages.
 
-:::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)
+:::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