Merge branch 'MicrosoftDocs:main' into DWDatabasesinAG

Author: MikeRayMSFT

.github/workflows/signoff-review.yml

@@ -98,10 +98,10 @@ jobs:
                 $ApprovedRegex = "\s*$ApprovedString\s*"
 
                 $EscalationEmail = "[Data Docs Team](mailto:[email protected]?subject=[PR%20REVIEW]%20Question%20on%20$GitHubRepoName%20PR%20$PrIssueNumber&body=$PrGitHubLink)"
-                $ContentLeadsUrl = "[content lead in your area](https://dev.azure.com/msft-skilling/Content/_dashboards/dashboard/b25043af-cab3-4b2c-8aac-9e8da15a796b)"
+                $ContentLeadsUrl = "[the content lead in your area](https://dev.azure.com/msft-skilling/Content/_dashboards/dashboard/b25043af-cab3-4b2c-8aac-9e8da15a796b)"
                 $PROpenMessage = "Thank you for your contribution! All PRs will be reviewed and approved by the content team. They will remain in a pending state until approved even after they successfully build and stage. When you are ready for the content team to publish this PR, sign off as normal. If you have any questions, please reach out to $ContentLeadsUrl or email the $EscalationEmail."
                 $NeedsContentTeamReviewMessage = "The content team will review this pr and work with you to publish your changes. Thank you for working with us to improve content quality for our customers!`n`n**To expedite your review**, please reach out to $ContentLeadsUrl or email the $EscalationEmail."
-                $CurrentlyInReviewMessage = "This PR is currently assigned to the content team for review. It must be reviewed and approved by the content team before merging.`n`n**To expedite your review**, please reach out to the $ContentLeadsUrl or email the $EscalationEmail."
+                $CurrentlyInReviewMessage = "This PR is currently assigned to the content team for review. It must be reviewed and approved by the content team before merging.`n`n**To expedite your review**, please reach out to ContentLeadsUrl or email the $EscalationEmail."
                 $AssignedReviewerMessage = "Assigning the pull request to @!!USER!! for review. #assign: !!USER!!"
                 $CheckFailed = $False
 
@@ -865,4 +865,4 @@ jobs:
 
                     # Force the workflow to fail so the validation failure can be tracked in Actions. In this workflow, this has no effect other than logging the failure.
                     Throw "User $CommentUser signed off but an unexpected error occurred. Please contact contact team to investigate the workflow. Sign off allowed to prevent blocking PRs."
-                }
+                }

.openpublishing.redirection.json

@@ -1,5 +1,69 @@
 {
   "redirections": [
+    {
+      "source_path": "docs/dea/database-experimentation-assistant-capture-trace.md",
+      "redirect_url": "/previous-versions/sql/dea/database-experimentation-assistant-capture-trace",
+      "redirect_document_id": false,
+      "monikers": [
+        "sql-server-ver16"
+      ]
+    },
+    {
+      "source_path": "docs/dea/database-experimentation-assistant-configure-replay.md",
+      "redirect_url": "/previous-versions/sql/dea/database-experimentation-assistant-configure-replay",
+      "redirect_document_id": false,
+      "monikers": [
+        "sql-server-ver16"
+      ]
+    },
+    {
+      "source_path": "docs/dea/database-experimentation-assistant-create-report.md",
+      "redirect_url": "/previous-versions/sql/dea/database-experimentation-assistant-create-report",
+      "redirect_document_id": false,
+      "monikers": [
+        "sql-server-ver16"
+      ]
+    },
+    {
+      "source_path": "docs/dea/database-experimentation-assistant-get-started.md",
+      "redirect_url": "/previous-versions/sql/dea/database-experimentation-assistant-get-started",
+      "redirect_document_id": false,
+      "monikers": [
+        "sql-server-ver16"
+      ]
+    },
+    {
+      "source_path": "docs/dea/database-experimentation-assistant-overview.md",
+      "redirect_url": "/previous-versions/sql/dea/database-experimentation-assistant-overview",
+      "redirect_document_id": false,
+      "monikers": [
+        "sql-server-ver16"
+      ]
+    },
+    {
+      "source_path": "docs/dea/database-experimentation-assistant-replay-trace.md",
+      "redirect_url": "/previous-versions/sql/dea/database-experimentation-assistant-replay-trace",
+      "redirect_document_id": false,
+      "monikers": [
+        "sql-server-ver16"
+      ]
+    },
+    {
+      "source_path": "docs/dea/database-experimentation-assistant-run-command-prompt.md",
+      "redirect_url": "/previous-versions/sql/dea/database-experimentation-assistant-run-command-prompt",
+      "redirect_document_id": false,
+      "monikers": [
+        "sql-server-ver16"
+      ]
+    },
+    {
+      "source_path": "docs/dea/database-experimentation-assistant-view-report.md",
+      "redirect_url": "/previous-versions/sql/dea/database-experimentation-assistant-view-report",
+      "redirect_document_id": false,
+      "monikers": [
+        "sql-server-ver16"
+      ]
+    },
     {
       "source_path": "docs/ado/ado-glossary.md",
       "redirect_url": "/previous-versions/sql/ado/ado-glossary",
@@ -67065,6 +67129,66 @@
     {
       "source_path": "docs/database-engine/availability-groups/windows/availability-replica-is-disconnected.md",
       "redirect_url": "/troubleshoot/sql/database-engine/availability-groups/availability-replica-is-disconnected"
+    },
+    {
+      "source_path": "docs/relational-databases/data-tier-applications/data-tier-applications.md",
+      "redirect_url": "/sql/tools/sql-database-projects/concepts/data-tier-applications/overview",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "docs/relational-databases/data-tier-applications/delete-a-data-tier-application.md",
+      "redirect_url": "/sql/tools/sql-database-projects/concepts/data-tier-applications/delete-data-tier-application",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "docs/relational-databases/data-tier-applications/deploy-a-data-tier-application.md",
+      "redirect_url": "/sql/tools/sql-database-projects/concepts/data-tier-applications/deploy-data-tier-application",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "docs/relational-databases/data-tier-applications/upgrade-a-data-tier-application.md",
+      "redirect_url": "/sql/tools/sql-database-projects/concepts/data-tier-applications/deploy-data-tier-application",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "docs/ssdt/extract-publish-and-register-dacpac-files.md",
+      "redirect_url": "/sql/tools/sql-database-projects/concepts/data-tier-applications/overview",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "docs/relational-databases/data-tier-applications/import-a-bacpac-file-to-create-a-new-user-database.md",
+      "redirect_url": "/sql/tools/sql-database-projects/concepts/data-tier-applications/import-bacpac-file-create-new-database",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "docs/relational-databases/data-tier-applications/deploy-a-database-by-using-a-dac.md",
+      "redirect_url": "/sql/tools/sql-database-projects/concepts/data-tier-applications/import-bacpac-file-create-new-database",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "docs/relational-databases/data-tier-applications/export-a-data-tier-application.md",
+      "redirect_url": "/sql/tools/sql-database-projects/concepts/data-tier-applications/export-bacpac-file",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "docs/relational-databases/data-tier-applications/extract-a-dac-from-a-database.md",
+      "redirect_url": "/sql/tools/sql-database-projects/concepts/data-tier-applications/extract-dacpac-from-database",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "docs/relational-databases/data-tier-applications/register-a-database-as-a-dac.md",
+      "redirect_url": "/sql/tools/sql-database-projects/concepts/data-tier-applications/register-database-as-dac",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "docs/relational-databases/data-tier-applications/unpack-a-dac-package.md",
+      "redirect_url": "/sql/tools/sql-database-projects/concepts/data-tier-applications/unpack-dacpac-file",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "docs/relational-databases/data-tier-applications/validate-a-dac-package.md",
+      "redirect_url": "/sql/tools/sql-database-projects/concepts/data-tier-applications/unpack-dacpac-file",
+      "redirect_document_id": false
     }
   ]
 }

azure-sql/database-watcher-overview.md

@@ -5,7 +5,7 @@ description: An overview of database watcher for Azure SQL, a managed monitoring
 author: dimitri-furman
 ms.author: dfurman
 ms.reviewer: wiassaf
-ms.date: 02/21/2024
+ms.date: 03/13/2025
 ms.service: azure-sql
 ms.subservice: monitoring
 ms.topic: conceptual
@@ -250,6 +250,7 @@ During preview, database watcher has the following known issues.
 | Data is not collected if you use a database in Real-Time Analytics as the data store, and the **OneLake availability** option is enabled. | Disable the **OneLake availability** option and restart the watcher to resume data collection. |
 | Because of a known issue in Azure SQL Database, data in the **Backup history** dataset for Azure SQL databases is not collected if the database catalog collation is other than the default `SQL_Latin1_General_CP1_CI_AS`. | None at this time. |
 | Because of a known issue in Azure Monitor Alerts, if you edit an alert rule created from a database watcher template, the scope of any fired alert will be set to the Azure Data Explorer cluster used as the watcher data store instead of the SQL target that the alert applies to. | Edit the alert rule programmatically, for example using Bicep or an ARM template, and set the `resourceIdColumn` property to the value `resource_id`. For more information, see [Resource Manager template samples for log search alert rules in Azure Monitor](/azure/azure-monitor/alerts/resource-manager-alerts-log). |
+| A database watcher deployment via Bicep, an ARM template, Terraform, or REST API fails if the **subscription ID**, **resource group name**, or **watcher name** deployment parameters use inconsistent casing. For example, adding a SQL target for an existing watcher named `example-watcher` fails if the deployment parameter uses `Example-Watcher` as the parameter value. | Use consistent casing for string parameters. For example, standardize on the lower case. |
 
 ## Troubleshoot
 

azure-sql/database/auditing-overview.md

@@ -5,7 +5,7 @@ description: SQL Auditing for Azure SQL Database and Azure Synapse Analytics tra
 author: sravanisaluru
 ms.author: srsaluru
 ms.reviewer: wiassaf, vanto, mathoma
-ms.date: 09/16/2024
+ms.date: 03/12/2025
 ms.service: azure-sql-database
 ms.subservice: security
 ms.topic: conceptual
@@ -17,7 +17,7 @@ ms.custom:
 
 [!INCLUDE [appliesto-sqldb-asa](../includes/appliesto-sqldb-asa.md)]
 
-Auditing for [What is Azure SQL Database?](sql-database-paas-overview.md) and [Azure Synapse Analytics](/azure/synapse-analytics/sql-data-warehouse/sql-data-warehouse-overview-what-is) tracks database events and writes them to an audit log in your Azure storage account, Log Analytics workspace, or Event Hubs.
+Auditing for [Azure SQL Database](sql-database-paas-overview.md) and [Azure Synapse Analytics](/azure/synapse-analytics/sql-data-warehouse/sql-data-warehouse-overview-what-is) tracks database events and writes them to an audit log in your Azure storage account, Log Analytics workspace, or Event Hubs.
 
 Auditing also:
 
@@ -39,11 +39,27 @@ You can use SQL Database auditing to:
 > [!IMPORTANT]  
 > Auditing for Azure SQL Database, Azure Synapse Analytics SQL pools, and Azure SQL Managed Instance is optimized for availability and performance of the database or instance being audited. During periods of very high activity or high network load, the auditing feature might allow transactions to proceed without recording all of the events marked for auditing.
 
+## Enhancements to performance, availability, and reliability in server auditing for Azure SQL Database (March 2025)
+
+- Re-architected major portions of SQL Auditing resulting in increased availability and reliability of server audits. As an added benefit, there's closer feature alignment with SQL Server and Azure SQL Managed Instance. Database auditing remains unchanged. 
+- The previous design of auditing triggers a database level audit and executes one audit session for each database in the server. The new architecture of auditing creates one extended event session at the server level that captures audit events for all databases.
+- The new auditing design optimizes memory and CPU, and is consistent with how auditing works in SQL Server and Azure SQL Managed Instance.
+
+### Changes from the re-architecture of server auditing 
+
+- Folder structure change for storage account:
+  - One of the primary changes involves a folder structure change for audit logs stored in storage account containers. Previously, server audit logs were written to separate folders; one for each database, with the database name serving as the folder name. With the new update, all server audit logs will be consolidated into a single folder labeled `master`. This behavior is the same as Azure SQL Managed Instance and SQL Server.
+- Folder structure change for read-only replicas:
+  - Read-only database replicas previously had their logs stored in a read-only folder. Those logs will now be written into the `master` folder. You can retrieve these logs by filtering on the new column `is_secondary_replica_true`.
+- Permissions required to view Audit logs :
+  - **Control Server** permission is required to view audit logs stored in the `master` folder
+
 ## Auditing limitations
 
 - Enabling auditing on a paused **Azure Synapse SQL pool** isn't supported. To enable auditing, resume the **Synapse SQL pool**.
 - Enabling auditing by using User Assigned Managed Identity (UAMI) isn't supported on **Azure Synapse**.
 - Currently, managed identities aren't supported for Azure Synapse, unless the storage account is behind a virtual network or firewall.
+- Due to performance constraints, we don't audit the **tempdb** and **temporary tables**. While the batch completed action group captures statements against temporary tables, it might not correctly populate the object names. However, the source table is always audited, ensuring that all inserts from the source table to temporary tables are recorded.
 - Auditing for **Azure Synapse SQL pools** supports default audit action groups **only**.
 - When you configure auditing for a [logical server in Azure](logical-servers.md) or Azure SQL Database with the log destination as a storage account, the authentication mode must match the configuration for that storage account. If using storage access keys as the authentication type, the target storage account must be enabled with access to the storage account keys. If the storage account is configured to only use authentication with Microsoft Entra ID ([formerly Azure Active Directory](/entra/fundamentals/new-name)), auditing can be configured to use managed identities for authentication.
 
@@ -64,7 +80,7 @@ You can use SQL Database auditing to:
 
 ## Related content
 
-- [What's New in Azure SQL Auditing](/Shows/Data-Exposed/Whats-New-in-Azure-SQL-Auditing)
+- [What's New in Azure SQL Auditing](/shows/data-exposed/server-audit-redesign-for-azure-sql-database-data-exposed)
 - [Get started with Azure SQL Managed Instance auditing](../managed-instance/auditing-configure.md)
 - [Auditing for SQL Server](/sql/relational-databases/security/auditing/sql-server-audit-database-engine)
 - [Set up Auditing for Azure SQL Database and Azure Synapse Analytics](auditing-setup.md)

azure-sql/database/automated-backups-change-settings.md

@@ -10,7 +10,6 @@ ms.service: azure-sql-database
 ms.subservice: backup-restore
 ms.topic: how-to
 ms.custom:
-  - references_regions
   - devx-track-azurepowershell
   - devx-track-azurecli
   - azure-sql-split

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

@@ -5,12 +5,11 @@ description: Learn how Azure SQL Database automatically backs up all databases a
 author: WilliamDAssafMSFT
 ms.author: wiassaf
 ms.reviewer: mathoma, danil, dinethi
-ms.date: 02/03/2025
+ms.date: 03/03/2025
 ms.service: azure-sql-database
 ms.subservice: backup-restore
 ms.topic: conceptual
 ms.custom:
-  - references_regions
   - azure-sql-split
   - build-2024
   - ignite-2024
@@ -77,7 +76,7 @@ You can choose one of the following storage redundancies for backups:
 
    :::image type="content" source="media/automated-backups-overview/multi-paired-zrs.svg" alt-text="Diagram showing the zone-redundant storage (ZRS) option.":::
 
-- **Geo-redundant storage (GRS)**: Copies your backups synchronously three times within a single physical location in the primary region by using LRS. Then it copies your data asynchronously three times to a single physical location in the [paired](/azure/reliability/cross-region-replication-azure#azure-cross-region-replication-pairings-for-all-geographies) secondary region. 
+- **Geo-redundant storage (GRS)**: Copies your backups synchronously three times within a single physical location in the primary region by using LRS. Then it copies your data asynchronously three times to a single physical location in the [paired secondary region](/azure/reliability/cross-region-replication-azure#azure-cross-region-replication-pairings-for-all-geographies). 
 
   The result is:
 
@@ -86,7 +85,7 @@ You can choose one of the following storage redundancies for backups:
 
    :::image type="content" source="media/automated-backups-overview/multi-paired-grs.svg" alt-text="Diagram showing the geo-redundant storage (GRS) option.":::
 
-- **Geo-Zone redundant storage (GZRS)**: Geo-zone-redundant storage (GZRS) combines the high availability provided by redundancy across availability zones (ZRS) with protection from regional outages provided by geo-replication (GRS). Copies your backups synchronously across three Azure availability zones in the primary region, and asynchronously three times to a single physical location in the [paired secondary region](/azure/reliability/cross-region-replication-azure#azure-cross-region-replication-pairings-for-all-geographies).
+- **Geo-Zone redundant storage (GZRS)** (preview): Geo-zone-redundant storage (GZRS) combines the high availability provided by redundancy across availability zones (ZRS) with protection from regional outages provided by geo-replication (GRS). Copies your backups synchronously across three Azure availability zones in the primary region, and asynchronously three times to a single physical location in the [paired secondary region](/azure/reliability/cross-region-replication-azure#azure-cross-region-replication-pairings-for-all-geographies). This feature is currently in preview.
 
    Microsoft recommends using GZRS for applications requiring maximum consistency, durability, and availability, excellent performance, and resilience for disaster recovery.
 
@@ -132,7 +131,7 @@ Automatic backups on secondary replicas:
 - Bring improved performance and predictability to the Business Critical service tier.
 
 > [!NOTE]
-> - Create a Microsoft support ticket to disable the feature for your instance. 
+> Create a Microsoft support ticket to disable the feature for your instance. 
 
 ## <a id="restore-capabilities"></a> Restore capabilities and features