Skip to content

Commit 1d29a6f

Browse files
authored
Merge pull request #34295 from MicrosoftDocs/main
6/4/2025 AM Publish
2 parents 9f166c8 + 6e84f7d commit 1d29a6f

File tree

698 files changed

+3711
-2511
lines changed

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

698 files changed

+3711
-2511
lines changed

azure-sql/database/ai-artificial-intelligence-intelligent-applications.md

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -11,6 +11,7 @@ ms.collection:
1111
- ce-skilling-ai-copilot
1212
ms.custom:
1313
- ignite-2024
14+
- build-2025
1415
monikerRange: "=azuresql || =azuresql-db || =fabricsql"
1516
---
1617
# Intelligent applications

azure-sql/database/authentication-microsoft-entra-create-users-with-nonunique-names.md

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -11,6 +11,7 @@ ms.subservice: security
1111
ms.topic: conceptual
1212
ms.custom:
1313
- ignite-2024
14+
- build-2025
1415
monikerRange: "=azuresql || =azuresql-db || =azuresql-mi || =fabricsql"
1516
---
1617

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/database/doc-changes-updates-release-notes-whats-new-archive.md

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -9,6 +9,8 @@ ms.date: 03/18/2025
99
ms.service: azure-sql-database
1010
ms.subservice: service-overview
1111
ms.topic: whats-new
12+
ms.custom:
13+
- build-2025
1214
---
1315

1416
# What's new in Azure SQL Database? (Archive)

azure-sql/database/doc-changes-updates-release-notes-whats-new.md

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -12,6 +12,7 @@ ms.topic: whats-new
1212
ms.custom:
1313
- build-2024
1414
- ignite-2024
15+
- build-2025
1516
monikerRange: "=azuresql || =azuresql-db"
1617
---
1718
# What's new in Azure SQL Database?

azure-sql/database/hyperscale-performance-diagnostics.md

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -8,7 +8,9 @@ ms.date: 04/28/2025
88
ms.service: azure-sql-database
99
ms.subservice: performance
1010
ms.topic: troubleshooting
11-
ms.custom: sqldbrb=1
11+
ms.custom:
12+
- sqldbrb=1
13+
- build-2025
1214
---
1315

1416
# SQL Hyperscale performance troubleshooting diagnostics

azure-sql/database/resource-limits-logical-server.md

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -8,6 +8,8 @@ ms.date: 04/28/2025
88
ms.service: azure-sql-database
99
ms.subservice: service-overview
1010
ms.topic: reference
11+
ms.custom:
12+
- build-2025
1113
---
1214
# Resource management in Azure SQL Database
1315

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

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -8,6 +8,8 @@ ms.date: 04/28/2025
88
ms.service: azure-sql-database
99
ms.subservice: elastic-pools
1010
ms.topic: reference
11+
ms.custom:
12+
- build-2025
1113
---
1214
# Resource limits for elastic pools using the vCore purchasing model
1315
[!INCLUDE [appliesto-sqldb](../includes/appliesto-sqldb.md)]

azure-sql/database/resource-limits-vcore-single-databases.md

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -10,6 +10,7 @@ ms.subservice: service-overview
1010
ms.topic: reference
1111
ms.custom:
1212
- sqldbrb=1
13+
- build-2025
1314
---
1415
# Resource limits for single databases using the vCore purchasing model
1516
[!INCLUDE[appliesto-sqldb](../includes/appliesto-sqldb.md)]

azure-sql/database/service-tier-hyperscale-frequently-asked-questions-faq.yml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@ metadata:
55
services: sql-database
66
ms.service: azure-sql-database
77
ms.subservice: service-overview
8-
ms.custom: sqldbrb=1
8+
ms.custom: sqldbrb=1, build-2025
99
ms.devlang:
1010
ms.topic: faq
1111
author: WilliamDAssafMSFT

0 commit comments

Comments
 (0)