Skip to content

Commit a511710

Browse files
authored
Merge pull request #97644 from JasonWHowell/patch-5
updating link
2 parents 5e32ce2 + a853bd7 commit a511710

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

articles/sql-database/sql-database-features.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -30,7 +30,7 @@ The following table lists the major features of SQL Server and provides informat
3030
| **SQL Feature** | **Single databases and elastic pools** | **Managed instances and instance pools** |
3131
| --- | --- | --- |
3232
| [Always Encrypted](https://docs.microsoft.com/sql/relational-databases/security/encryption/always-encrypted-database-engine) | Yes - see [Cert store](sql-database-always-encrypted.md) and [Key vault](sql-database-always-encrypted-azure-key-vault.md) | Yes - see [Cert store](sql-database-always-encrypted.md) and [Key vault](sql-database-always-encrypted-azure-key-vault.md) |
33-
| [Always On Availability Groups](https://docs.microsoft.com/sql/database-engine/availability-groups/windows/always-on-availability-groups-sql-server) | [99.99-99.995% availability](sql-database-high-availability.md) is guaranteed for every database. Disaster recovery is discussed in [Overview of business continuity with Azure SQL Database](sql-database-business-continuity.md) | [99.99.% availability](sql-database-high-availability.md) is guaranteed for every database and [cannot be managed by user](sql-database-managed-instance-transact-sql-information.md#always-on-availability-groups). Disaster recovery is discussed in [Overview of business continuity with Azure SQL Database](sql-database-business-continuity.md). Use [Auto-failover groups](sql-database-auto-failover-group.md) to configure secondary Always On Managed Instance in another region. Other SQL Server instances and Single databases cannot be used as secondaries for Managed Instance. |
33+
| [Always On Availability Groups](https://docs.microsoft.com/sql/database-engine/availability-groups/windows/always-on-availability-groups-sql-server) | [99.99-99.995% availability](sql-database-high-availability.md) is guaranteed for every database. Disaster recovery is discussed in [Overview of business continuity with Azure SQL Database](sql-database-business-continuity.md) | [99.99.% availability](sql-database-high-availability.md) is guaranteed for every database and [cannot be managed by user](sql-database-managed-instance-transact-sql-information.md#availability). Disaster recovery is discussed in [Overview of business continuity with Azure SQL Database](sql-database-business-continuity.md). Use [Auto-failover groups](sql-database-auto-failover-group.md) to configure secondary Always On Managed Instance in another region. Other SQL Server instances and Single databases cannot be used as secondaries for Managed Instance. |
3434
| [Attach a database](https://docs.microsoft.com/sql/relational-databases/databases/attach-a-database) | No | No |
3535
| [Auditing](https://docs.microsoft.com/sql/relational-databases/security/auditing/sql-server-audit-database-engine) | [Yes](sql-database-auditing.md)| [Yes](sql-database-managed-instance-auditing.md), with some [differences](sql-database-managed-instance-transact-sql-information.md#auditing) |
3636
| [Azure Active Directory (AAD) authentication](sql-database-aad-authentication.md) | Yes. AAD users only. | Yes. Including server-level AAD logins. |

0 commit comments

Comments
 (0)