Skip to content

Commit a8abb30

Browse files
authored
Merge pull request #88905 from MashaMSFT/20190917_fogpreview
removed preview from FOG for MI
2 parents 0d16d6f + 068a2a0 commit a8abb30

6 files changed

+6
-10
lines changed

articles/sql-database/sql-database-active-geo-replication-portal.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -16,7 +16,7 @@ ms.date: 02/13/2019
1616

1717
This article shows you how to configure [active geo-replication for single and pooled databases](sql-database-active-geo-replication.md#active-geo-replication-terminology-and-capabilities) in Azure SQL Database using the [Azure portal](https://portal.azure.com) and to initiate failover.
1818

19-
For information about auto-failover groups with single and pooled databases, see [Best practices of using failover groups with single and pooled databases](sql-database-auto-failover-group.md#best-practices-of-using-failover-groups-with-single-databases-and-elastic-pools). For information about auto-failover groups with Managed Instances (preview), see [Best practices of using failover groups with managed-instances](sql-database-auto-failover-group.md#best-practices-of-using-failover-groups-with-managed-instances).
19+
For information about auto-failover groups with single and pooled databases, see [Best practices of using failover groups with single and pooled databases](sql-database-auto-failover-group.md#best-practices-of-using-failover-groups-with-single-databases-and-elastic-pools). For information about auto-failover groups with Managed Instances, see [Best practices of using failover groups with managed-instances](sql-database-auto-failover-group.md#best-practices-of-using-failover-groups-with-managed-instances).
2020

2121
## Prerequisites
2222

articles/sql-database/sql-database-auto-failover-group.md

Lines changed: 1 addition & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -168,9 +168,6 @@ When designing a service with business continuity in mind, follow these general
168168
169169
## Best practices of using failover groups with managed instances
170170

171-
> [!IMPORTANT]
172-
> Auto-failover groups for Managed Instance is in public preview.
173-
174171
The auto-failover group must be configured on the primary instance and will connect it to the secondary instance in a different Azure region. All databases in the instance will be replicated to the secondary instance.
175172

176173
The following diagram illustrates a typical configuration of a geo-redundant cloud application using managed instance and auto-failover group.
@@ -360,7 +357,7 @@ As discussed previously, auto-failover groups and active geo-replication can als
360357
| [Update Failover Group](https://docs.microsoft.com/rest/api/sql/failovergroups/update) | Updates a failover group. |
361358
| | |
362359

363-
### REST API: Manage failover groups with Managed Instances (preview)
360+
### REST API: Manage failover groups with Managed Instances
364361

365362
| API | Description |
366363
| --- | --- |

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

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -109,8 +109,8 @@ Azure platform provides a number of PaaS capabilities that are added as an addit
109109

110110
| **Platform Feature** | **Single databases and elastic pools** | **Managed instances and instance pools** |
111111
| --- | --- | --- |
112-
| [Active geo-replication](sql-database-active-geo-replication.md) | Yes - all service tiers other than hyperscale | No, see [Auto-failover groups(preview)](sql-database-auto-failover-group.md) as an alternative |
113-
| [Auto-failover groups](sql-database-auto-failover-group.md) | Yes - all service tiers other than hyperscale | Yes, in [public preview](sql-database-auto-failover-group.md)|
112+
| [Active geo-replication](sql-database-active-geo-replication.md) | Yes - all service tiers other than hyperscale | No, see [Auto-failover groups](sql-database-auto-failover-group.md) as an alternative |
113+
| [Auto-failover groups](sql-database-auto-failover-group.md) | Yes - all service tiers other than hyperscale | Yes, see [Auto-failover groups](sql-database-auto-failover-group.md)|
114114
| Auto-scale | Yes, but only in [serverless model](sql-database-serverless.md). In the non-serverless model, the change of service tier (change of vCore, storage, or DTU) is fast and online. The service tier change requires minimal or no downtime. | No, you need to choose reserved compute and storage. The change of service tier (vCore or max storage) is online and requires minimal or no downtime. |
115115
| [Automatic backups](sql-database-automated-backups.md) | Yes. Full backups are taken every 7 days, differential 12 hours, and log backups every 5-10 min. | Yes. Full backups are taken every 7 days, differential 12 hours, and log backups every 5-10 min. |
116116
| [Automatic tuning (indexes)](https://docs.microsoft.com/sql/relational-databases/automatic-tuning/automatic-tuning)| [Yes](sql-database-automatic-tuning.md)| No |

articles/sql-database/sql-database-managed-instance-failover-group-tutorial.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -25,7 +25,7 @@ Add a SQL Database managed instance to a failover group. In this article, you wi
2525
> [!NOTE]
2626
> - When going through this tutorial, ensure you are configuring your resources with the [prerequisites for setting up failover groups for managed instance](sql-database-auto-failover-group.md#enabling-geo-replication-between-managed-instances-and-their-vnets).
2727
> - Creating a managed instance can take a significant amount of time. As a result, this tutorial could take several hours to complete. For more information on provisioning times, see [managed instance management operations](sql-database-managed-instance.md#managed-instance-management-operations).
28-
> - Using failover groups with managed instances is currently in preview.
28+
2929

3030
## Prerequisites
3131

articles/sql-database/sql-database-managed-instance-get-started.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -54,7 +54,7 @@ The following steps show you how to create a managed instance.
5454

5555
![Managed instance form](./media/sql-database-managed-instance-get-started/managed-instance-create-form.png)
5656

57-
5. To use the managed instance as an instance failover group secondary, select the checkout and specify the DnsAzurePartner managed instance. This feature is in preview and isn't shown in the following screenshot.
57+
5. To use the managed instance as an instance failover group secondary, select the checkout and specify the DnsAzurePartner managed instance.
5858
6. Select **Pricing tier** to size compute and storage resources and to review the pricing tier options. The General Purpose pricing tier with 32 GB of memory and 16 vCores is the default value.
5959
7. Use the sliders or text boxes to specify the amount of storage and the number of virtual cores.
6060
8. When you're finished, select **Apply** to save your selection.

articles/sql-database/sql-database-release-notes.md

Lines changed: 0 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -42,7 +42,6 @@ This article lists SQL Database features that are currently in public preview. F
4242
| ---| --- |
4343
| <a href="/azure/sql-database/sql-database-instance-pools">Instance pools</a> | A convenient and cost-efficient way to migrate smaller SQL instances to the cloud. |
4444
| <a href="https://aka.ms/managed-instance-tde-byok">Transparent data encryption (TDE) with Bring Your Own Key (BYOK)</a> |For information, see [Azure SQL Transparent Data Encryption with customer-managed keys in Azure Key Vault: Bring Your Own Key support](transparent-data-encryption-byok-azure-sql.md).|
45-
| <a href="https://aka.ms/managed-instance-failover-groups">Geo-distributed failover groups</a> | Keep a copy of the instance in another region and ensure that your data will be available even in the regional disaster scenario. |
4645
| <a href="https://aka.ms/managed-instance-aadlogins">Instance-level Azure AD server principals (logins)</a> | Create server-level logins using <a href="https://docs.microsoft.com/sql/t-sql/statements/create-login-transact-sql?view=azuresqldb-mi-current">CREATE LOGIN FROM EXTERNAL PROVIDER</a> statement. |
4746
| [Transactional Replication](sql-database-managed-instance-transactional-replication.md) | Replicate the changes from your tables into other databases placed on Managed Instances, Single Databases, or SQL Server instances, or update your tables when some rows are changed in other Managed Instances or SQL Server instance. For information, see [Configure replication in an Azure SQL Database managed instance database](replication-with-sql-database-managed-instance.md). |
4847
| Threat detection |For information, see [Configure threat detection in Azure SQL Database managed instance](sql-database-managed-instance-threat-detection.md).|

0 commit comments

Comments
 (0)