Skip to content

Commit 3b66914

Browse files
MashaMSFTtiagodiasfernandessravanisaluruJamesFerebeebaleng
authored
Adding registerallprovidersip setting (#34112)
* Update availability-group-manually-configure-tutorial-multi-subnet.md * Learn Editor: Update sql-server-audit-action-groups-and-actions.md Learn Editor: Update sql-server-audit-action-groups-and-actions.md fixes adding workaround * Add database fabric reference adding sql db in fabric as a replication subscriber for sql mi adding note staging tables * Update mssqlserver-2814-database-engine-error.md adding all the others map_values sys.dm_xe_map_values for statement_recompile_cause * a few more changes --------- Co-authored-by: tiagofe <[email protected]> Co-authored-by: sravani saluru <[email protected]> Co-authored-by: James Ferebee <[email protected]> Co-authored-by: antonio piero emanuele viarengo <[email protected]>
1 parent 5d26240 commit 3b66914

12 files changed

+73
-23
lines changed

‎azure-sql/database/automated-backups-overview.md

Lines changed: 3 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -169,7 +169,6 @@ To perform a restore, see [Restore a database from backups](recovery-using-backu
169169
| **Restore a deleted database** | [SQL Database](recovery-using-backups.md)<br>[SQL Managed Instance](../managed-instance/point-in-time-restore.md#restore-a-deleted-database) | [SQL Database](long-term-backup-retention-configure.md#restore-from-ltr-backups) <br/> [SQL Managed Instance](../managed-instance/long-term-backup-retention-configure.md#restore-from-ltr-backups) | [SQL Database](/powershell/module/az.sql/get-azsqldeleteddatabasebackup) <br/> [SQL Managed Instance](/powershell/module/az.sql/get-azsqldeletedinstancedatabasebackup)|
170170

171171

172-
173172
## Export a database
174173

175174
Automatic backups taken by the Azure service are not available to download or access directly. They can only be used for restore operations through Azure.
@@ -209,7 +208,7 @@ For all databases, including [TDE-encrypted](../database/transparent-data-encryp
209208
Azure SQL Database computes your total used backup storage as a cumulative value. Every hour, this value is reported to the Azure billing pipeline. The pipeline is responsible for aggregating this hourly usage to calculate your consumption at the end of each month. After the database is deleted, consumption decreases as backups age out and are deleted. After all backups are deleted and PITR is no longer possible, billing stops.
210209

211210
> [!IMPORTANT]
212-
> Backups of a database are retained to provide PITR even if the database has been deleted. Although deleting and re-creating a database might save storage and compute costs, it might increase backup storage costs. The reason is that the service retains backups for each deleted database, every time it's deleted.
211+
> Backups of a database are retained to provide PITR even if the database has been deleted. Although deleting and recreating a database might save storage and compute costs, it might increase backup storage costs. The reason is that the service retains backups for each deleted database, every time it's deleted.
213212
214213
### Monitor consumption
215214

@@ -351,6 +350,8 @@ All database backups are taken with the CHECKSUM option to provide additional ba
351350

352351
Azure SQL Database backups are managed entirely within Microsoft-owned Azure subscriptions using secure, internal Azure Storage accounts. These backups are not accessible externally, ensuring strong data isolation and protection. Within Microsoft, only backend services such as the Backup-Restore service has access to create, copy or restore these backups. Microsoft engineers, including developers, do not have standing access. To minimize exposure and maximize security, Microsoft can only obtain Just-In-Time (JIT) access under strict audit controls when absolutely necessary to troubleshoot specific customer issues.
353352

353+
Backups are automatically deleted after the retention expires.
354+
354355
## Compliance through backup retention
355356

356357
If the default retention doesn't meet your compliance requirements, you can change the PITR retention period. For more information, see [Change the PITR backup retention period](automated-backups-change-settings.md#change-short-term-retention-policy).

‎azure-sql/managed-instance/automated-backups-overview.md

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -313,6 +313,8 @@ For a full list of built-in policy definitions for SQL Managed Instance, review
313313

314314
Azure SQL Managed Instance backups are managed entirely within Microsoft-owned Azure subscriptions using secure, internal Azure Storage accounts. These backups aren't accessible externally, ensuring strong data isolation and protection. Within Microsoft, only backend services such as the Backup-Restore service has access to create, copy or restore these backups. Microsoft engineers, including developers, don't have standing access. To minimize exposure and maximize security, Microsoft can only obtain Just-In-Time (JIT) access under strict audit controls when absolutely necessary to troubleshoot specific customer issues.
315315

316+
Backups are automatically deleted after the retention expires.
317+
316318
## Compliance through backup retention
317319

318320
If the default retention doesn't meet your compliance requirements, you can change the PITR retention period. For more information, see [Change the PITR backup retention period](automated-backups-change-settings.md#change-short-term-retention-policy).

‎azure-sql/managed-instance/log-replay-service-compare-mi-link.md

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -42,7 +42,8 @@ The following table compares both LRS and MI link in greater detail:
4242
|---|---|---|---|
4343
| **Underlying technology** | Distributed availability groups (AG) | Log shipping | MI link uses a distributed availability group for replication, which is newer and more advanced when compared to the log shipping technology used by LRS. |
4444
| **Replication performance** | Near real-time. | Restores every few minutes. | Replicating data through the MI link is considerably more performant than applying transaction log backups with LRS. |
45-
| **Minimal supported source database** | SQL Server 2016 and above | SQL Server 2008 and above | LRS can support much older SQL Server versions than MI link. |
45+
| **Minimum supported source version** | SQL Server 2016 and above | SQL Server 2008 and above | LRS can support much older SQL Server versions than MI link. |
46+
| **Minimum supported Windows Server version** | Windows Server 2012 R2 | Windows Server 2008 | LRS can support much older Windows Server versions than MI link. |
4647
| **Read-only secondary** | Supported. | Not supported. | While replication is in progress, SQL Managed Instance databases replicated through the link can be used for read-only workloads, which lets you test your migration before the cut over, or use your databases before migrating to Azure. Likewise, when you perform a reverse migration back to SQL Server 2022 and later, the database is accessible for read-only workloads on SQL Server while the migration is in progress. This capability isn't available with LRS. |
4748
| **Replication of TDE encrypted databases** | Yes, requires importing security keys to SQL Managed Instance. | Yes, requires importing security keys to SQL Managed Instance. | The requirement and procedure to migrate the corresponding encryption certificate from SQL Server to SQL managed instance before starting the migration is the same for both migration options. |
4849
| **Network connectivity type** | - Private endpoint <br /> - VPN configured with both inbound and outbound ports | Public endpoint |While MI link provides additional layers of security, and offers a VPN as an option, networking is more difficult to configure compared to LRS. <br /><br /> By default, LRS provides a simplified experience so you can use it immediately without any network or VPN configuration. LRS uses a public endpoint by default, which is less secure than the VPN used with MI link, and it might not satisfy some of the most demanding security requirements since it uses a publicly exposed Azure Blob storage account as an intermediary to save data before it's restored to SQL Managed Instance. While it's possible to use a private endpoint with LRS to make the transmission of data more secure, it increases initial configuration complexity. |

‎azure-sql/managed-instance/log-replay-service-migrate.md

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -52,6 +52,7 @@ Make sure that you meet the following requirements for SQL Server:
5252
- For SQL Server versions 2008 to 2016, take a backup locally and [manually upload](#copy-existing-backups-to-your-blob-storage-account) it to your Azure Blob Storage account.
5353
- For SQL Server 2016 and later, you can [take your backup directly](#take-backups-directly-to-your-blob-storage-account) to your Azure Blob Storage account.
5454
- Although having `CHECKSUM` enabled for backups isn't required, it's highly recommended to prevent unintentionally migrating a corrupt database, and for faster restore operations.
55+
- Any version of Windows Server is supported based on the SQL Server version supportability.
5556

5657
### Azure
5758

@@ -626,7 +627,8 @@ Consider the following limitations when migrating with LRS:
626627
- You must start LRS separately for each database that points to the full URI path that contains an individual database folder.
627628
- The backup URI path, container name, or folder names can't contain `backup` or `Backup` as these are reserved keywords.
628629
- When starting multiple Log Replay restores in parallel, targeting the same storage container, ensure that the same valid SAS token is provided for every restore operation.
629-
- LRS can support up to 100 simultaneous restore processes per single managed instance.
630+
- LRS supports migrating a total number of databases to a single instance up to the [resource limits](resource-limits.md#service-tier-characteristics) of the service tier. For example, you can restore up to 100 total databases in the **General Purpose** service tier, and up to 500 total databases in the **Next-Gen General Purpose** service tier.
631+
- LRS supports 100 simultaneous database restores to a single instance, and 200 simultaneous database restores for all instances in a single subscription. For example, you can restore 100 databases in parallel to two instances in the same subscription at the same time, or 50 databases in four simultaneous batches in parallel to four separate instances within the same subscription.
630632
- A single LRS job can run for a maximum of 30 days, after which it will be automatically canceled.
631633
- While it's possible to use an Azure Storage account behind a firewall, extra configuration is necessary, and the storage account and managed instance must either be in the same region, or two paired regions. Review [Configure firewall](log-replay-service-migrate.md#configure-azure-storage-behind-a-firewall) to learn more.
632634
- The maximum number of databases you can restore in parallel is 200 per single subscription. In some cases, it's possible to increase this limit by opening a support ticket.

‎azure-sql/managed-instance/managed-instance-link-feature-overview.md

Lines changed: 9 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@ description: This article describes the Managed Instance link, which you can use
55
author: djordje-jeremic
66
ms.author: djjeremi
77
ms.reviewer: mathoma, randolphwest
8-
ms.date: 03/06/2025
8+
ms.date: 05/27/2025
99
ms.service: azure-sql-managed-instance
1010
ms.subservice: data-movement
1111
ms.topic: concept-article
@@ -55,12 +55,13 @@ The following table lists the functionality of the link feature and the minimum
5555

5656
| Initial primary version | Operating system (OS) | One-way replication | Disaster recovery options | Servicing update requirement |
5757
| --- | --- | --- | --- | --- |
58-
| Azure SQL Managed Instance | Windows Server and Linux | Generally available | [Bi-directional](#disaster-recovery) | - [SQL Server 2022 CU10 (KB5031778)](/troubleshoot/sql/releases/sqlserver-2022/cumulativeupdate10): Creating a link from Azure SQL Managed Instance to SQL Server 2022 <sup>1</sup> <br /> - [SQL Server 2022 CU13 (KB5036432)](/troubleshoot/sql/releases/sqlserver-2022/cumulativeupdate13): Failing over the link using [Transact-SQL](managed-instance-link-failover-how-to.md?tabs=tsql#fail-over-a-database) <br /> - Configuring a link from Azure SQL Managed Instance to SQL Server 2022 is only supported by instances configured with the [**SQL Server 2022 update policy**](update-policy.md#sql-server-2022-update-policy) |
59-
| SQL Server 2022 (16.x) | Windows Server and Linux | Generally available | [Bi-directional](#disaster-recovery) | - SQL Server 2022 RTM: Creating a link from SQL Server 2022 to Azure SQL Managed Instance <br /> - [SQL Server 2022 CU13 (KB5036432)](/troubleshoot/sql/releases/sqlserver-2022/cumulativeupdate13): Failing over the link using [Transact-SQL](managed-instance-link-failover-how-to.md?tabs=tsql#fail-over-a-database) |
60-
| SQL Server 2019 (15.x) | Windows Server only | Generally available | From SQL Server to SQL MI only | [SQL Server 2019 CU20 (KB5024276)](https://support.microsoft.com/topic/kb5024276-cumulative-update-20-for-sql-server-2019-4b282be9-b559-46ac-9b6a-badbd44785d2) |
61-
| SQL Server 2017 (14.x) | Windows Server only | Generally available | From SQL Server to SQL MI only | The most recent [SQL Server 2017 CU31](/troubleshoot/sql/releases/sqlserver-2017/cumulativeupdate31) build and the matching [SQL Server 2017 Azure Connect pack](/troubleshoot/sql/releases/sqlserver-2017/azureconnect) build |
62-
| SQL Server 2016 (13.x) | Windows Server only | Generally available | From SQL Server to SQL MI only| The most recent [SQL Server 2016 SP3](/troubleshoot/sql/releases/sqlserver-2016/build-versions#sql-server-2016-service-pack-3-sp3-cumulative-update-cu-builds) build and the matching [SQL Server 2016 Azure Connect pack](/troubleshoot/sql/releases/sqlserver-2016/build-versions#sql-server-2016-service-pack-3-sp3-azure-connect-pack-builds) build |
63-
| SQL Server 2014 (12.x) and below | N/A | N/A | N/A | Versions before SQL Server 2016 aren't supported.|
58+
| Azure SQL Managed Instance | [Windows Server](/sql/sql-server/install/hardware-and-software-requirements-for-installing-sql-server-2022#operating-system-support) and [Linux](/sql/linux/sql-server-linux-setup#supported-platforms) for the secondary SQL Server instance replica | Generally available | [Bi-directional](#disaster-recovery) | - [SQL Server 2022 CU10 (KB5031778)](/troubleshoot/sql/releases/sqlserver-2022/cumulativeupdate10): Creating a link from Azure SQL Managed Instance to SQL Server 2022 <sup>1</sup> <br /> - [SQL Server 2022 CU13 (KB5036432)](/troubleshoot/sql/releases/sqlserver-2022/cumulativeupdate13): Failing over the link using [Transact-SQL](managed-instance-link-failover-how-to.md?tabs=tsql#fail-over-a-database) <br /> - Configuring a link from Azure SQL Managed Instance to SQL Server 2022 is only supported by instances configured with the [**SQL Server 2022 update policy**](update-policy.md#sql-server-2022-update-policy) |
59+
| SQL Server 2025 (17.x) Preview | [Windows Server](/sql/sql-server/install/hardware-and-software-requirements-for-installing-sql-server-2025#operating-system-support) and [Linux](/sql/linux/sql-server-linux-setup#supported-platforms) | Preview | From SQL Server to SQL MI only | [SQL Server 2025 Preview CTP 2.0](/sql/sql-server/sql-server-2025-release-notes) |
60+
| SQL Server 2022 (16.x) | [Windows Server](/sql/sql-server/install/hardware-and-software-requirements-for-installing-sql-server-2022#operating-system-support) and [Linux](/sql/linux/sql-server-linux-setup#supported-platforms) | Generally available | [Bi-directional](#disaster-recovery) | - SQL Server 2022 RTM: Creating a link from SQL Server 2022 to Azure SQL Managed Instance <br /> - [SQL Server 2022 CU13 (KB5036432)](/troubleshoot/sql/releases/sqlserver-2022/cumulativeupdate13): Failing over the link using [Transact-SQL](managed-instance-link-failover-how-to.md?tabs=tsql#fail-over-a-database) |
61+
| SQL Server 2019 (15.x) | [Windows Server only](/sql/sql-server/install/hardware-and-software-requirements-for-installing-sql-server-2019) | Generally available | From SQL Server to SQL MI only | [SQL Server 2019 CU20 (KB5024276)](https://support.microsoft.com/topic/kb5024276-cumulative-update-20-for-sql-server-2019-4b282be9-b559-46ac-9b6a-badbd44785d2) |
62+
| SQL Server 2017 (14.x) | [Windows Server only](/sql/sql-server/install/hardware-and-software-requirements-for-installing-sql-server#operating-system-support-for-sql-server-2017) | Generally available | From SQL Server to SQL MI only | The most recent [SQL Server 2017 CU31](/troubleshoot/sql/releases/sqlserver-2017/cumulativeupdate31) build and the matching [SQL Server 2017 Azure Connect pack](/troubleshoot/sql/releases/sqlserver-2017/azureconnect) build |
63+
| SQL Server 2016 (13.x) | [Windows Server only](/sql/sql-server/install/hardware-and-software-requirements-for-installing-sql-server#operating-system-support-for-sql-server-2017) | Generally available | From SQL Server to SQL MI only| The most recent [SQL Server 2016 SP3](/troubleshoot/sql/releases/sqlserver-2016/build-versions#sql-server-2016-service-pack-3-sp3-cumulative-update-cu-builds) build and the matching [SQL Server 2016 Azure Connect pack](/troubleshoot/sql/releases/sqlserver-2016/build-versions#sql-server-2016-service-pack-3-sp3-azure-connect-pack-builds) build |
64+
| SQL Server 2014 (12.x) and earlier | N/A | N/A | N/A | Versions before SQL Server 2016 aren't supported.|
6465

6566
<sup>1</sup> While creating a link with SQL Server 2022 as the initial primary is supported starting with the RTM version of SQL Server 2022, creating a link with Azure SQL Managed Instance as the initial primary is supported only starting with SQL Server 2022 CU10. If you create the link from a SQL Managed Instance initial primary, downgrading SQL Server below CU10 isn't supported while the link is active as it can cause issues after failing over in either direction.
6667

@@ -196,6 +197,7 @@ Configuration limitations include:
196197

197198
- If there are multiple SQL Server instances on a server, it's possible to configure a link with each instance, but each instance must be configured to use a separate database mirroring endpoint, with a dedicated port per instance. Only the default instance should use port 5022 for the database mirroring endpoint.
198199
- Only one database can be placed into a single availability group for one Managed Instance link. However, it's possible to replicate multiple databases in a single SQL Server instance by establishing multiple links.
200+
- It's possible to create a link with an existing availability group with a single database. If your existing availability group has multiple databases, you can create a link with the availability group only if you remove all databases except one from the availability group.
199201
- A single General Purpose or Business Critical SQL Managed Instance supports up to 100 links, and a single Next-gen General Purpose SQL Managed Instance supports up to 500 links, from the same, or from multiple SQL Server sources.
200202
- A Managed Instance link can replicate a database of any size if it fits into the chosen storage size of the target SQL Managed Instance deployment.
201203
- Managed Instance link authentication between SQL Server and SQL Managed Instance is certificate-based and available only through an exchange of certificates. Using Windows authentication to establish the link between the SQL Server instance and the managed instance isn't supported.

0 commit comments

Comments
 (0)