Merge pull request #32008 from MicrosoftDocs/main

10/08/2024 AM Publish

Author: Emma-yxf

.openpublishing.redirection.json

@@ -20335,6 +20335,11 @@
       "redirect_url": "/previous-versions/sql/2014/relational-databases/errors-events/database-engine-events-and-errors",
       "redirect_document_id": false
     },
+    {
+      "source_path": "docs/relational-databases/errors-events/database-engine-events-and-errors-41400-to-42999.md",
+      "redirect_url": "/sql/relational-databases/errors-events/database-engine-events-and-errors-41400-to-49999",
+      "redirect_document_id": false
+    },
     {
       "source_path": "docs/2014/relational-databases/errors-events/errors-and-events-reference-database-engine.md",
       "redirect_url": "/previous-versions/sql/2014/relational-databases/errors-events/errors-and-events-reference-database-engine",

azure-sql/accelerated-database-recovery.md

@@ -79,7 +79,7 @@ The ADR recovery process has the same three phases as the current recovery proce
 
   The process remains the same as before with the addition of reconstructing SLOG and copying log records for non-versioned operations.
 
-- **Redo** phase
+- **Redo phase**
 
   Broken into two phases (P)
   - Phase 1
@@ -140,7 +140,7 @@ The following types of workloads benefit most from ADR:
 
    - Many DDLs are executed in one transaction. For example, in one transaction, rapidly creating and dropping temp tables. 
 
-   - A table has very large number of partitions/indexes that are modified. For example, a DROP TABLE operation on such table would require a large reservation of SLOG memory, which would delay truncation of the transaction log and delay undo/redo operations. The workaround can be drop the indexes individually and gradually, then drop the table. For more information on the SLOG, see [ADR recovery components](/sql/relational-databases/accelerated-database-recovery-concepts).
+   - A table has very large number of partitions/indexes that are modified. For example, a DROP TABLE operation on such table would require a large reservation of SLOG memory, which would delay truncation of the transaction log and delay undo/redo operations. As a workaround, drop the indexes individually and gradually, then drop the table. For more information on the SLOG, see [ADR recovery components](/sql/relational-databases/accelerated-database-recovery-concepts).
 
 - Prevent or reduce unnecessary aborted situations. A high abort rate will put pressure on the PVS cleaner and lower ADR performance. The aborts may come from a high rate of deadlocks, duplicate keys, or other constraint violations.  
 

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

@@ -65,7 +65,7 @@ The following table lists features of Azure SQL Database that have been made gen
 
 | Feature | GA Month | Details |
 | --- | --- | --- |
-| [Lower auto-pause delay for serverless](serverless-tier-overview.md) |October 2024| Reduce costs by lowering the auto-pause delay for serverless compute in Azure SQL Database. [Learn more.](https://aka.ms/AAs7lpz) |
+| [Lower auto-pause delay for serverless](serverless-tier-overview.md) |October 2024| Reduce costs by lowering the [auto-pause delay for serverless compute in Azure SQL Database](https://aka.ms/AAs7lpz). |
 | [Hyperscale elastic pools](hyperscale-elastic-pool-overview.md) | September 2024 | Manage and scale multiple Hyperscale databases in Azure SQL Database by using Hyperscale elastic pools. Hyperscale elastic pools also support Premium-series hardware and zone redundancy. For more information, see [Hyperscale Elastic Pools are now generally available](https://aka.ms/hsep-ga). |
 | [Hyperscale elastic pool maintenance window support](maintenance-window.md) | September 2024 |You can configure a non-default [maintenance window](maintenance-window.md) for a [Hyperscale elastic pool](hyperscale-elastic-pool-overview.md). For more information, read [Blog: Maintenance window support for Azure SQL Database Hyperscale elastic pools](https://aka.ms/hsep-fmw). |
 | [CURRENT_DATE Transact-SQL](/sql/t-sql/functions/current-date-transact-sql) | August 2024 |  A Transact-SQL (T-SQL) function that returns the current database system date as a date value, without the database time and time zone offset. |
@@ -87,6 +87,12 @@ The following table lists features of Azure SQL Database that have been made gen
 
 Learn about significant changes to the Azure SQL Database documentation. For previous years, see the [What's new archive](doc-changes-updates-release-notes-whats-new-archive.md).
 
+### October 2024
+
+| Changes | Details |
+| --- | --- |
+| [Lower auto-pause delay for serverless](serverless-tier-overview.md) | Reduce costs by lowering the [auto-pause delay for serverless compute in Azure SQL Database](https://aka.ms/AAs7lpz). |
+
 ### September 2024
 
 | Changes | Details |

azure-sql/database/media/serverless-tier-overview/serverless-billing.png

@@ -23,6 +23,8 @@ Private Link allows you to connect to various PaaS services in Azure via a **pri
 > [!IMPORTANT]  
 > This article applies to both Azure SQL Database and [dedicated SQL pool (formerly SQL DW)](/azure/synapse-analytics/sql-data-warehouse/sql-data-warehouse-overview-what-is) in Azure Synapse Analytics. These settings apply to all SQL Database and dedicated SQL pool (formerly SQL DW) databases associated with the server. For simplicity, the term 'database' refers to both databases in Azure SQL Database and Azure Synapse Analytics. Likewise, any references to 'server' is referring to the [logical server](logical-servers.md) that hosts Azure SQL Database and dedicated SQL pool (formerly SQL DW) in Azure Synapse Analytics. This article does *not* apply to Azure SQL Managed Instance or dedicated SQL pools in Azure Synapse Analytics workspaces.
 
+<a id="how-to-set-up-private-link-for-azure-sql-database"></a>
+
 ## How to set up Private Link
 
 ### Creation process

azure-sql/database/private-endpoint-overview.md

@@ -71,7 +71,7 @@ The following table covers these SLOs: `GP_S_Gen5_1`, `GP_S_Gen5_2`, `GP_S_Gen5_
 |:-|-:|-:|-:|-:|-:|
 | Hardware | Gen5 | Gen5 | Gen5 | Gen5 | Gen5 |
 | Min-max memory (GB) | 2.02 - 3 | 2.05 - 6 | 2.10 - 12 | 2.25 - 18 | 3.00 - 24 |
-| Min-max auto-pause delay (minutes) | 60 - 10,080 | 60 - 10,080 | 60 - 10,080 | 60 - 10,080 | 60 - 10,080 |
+| Min-max auto-pause delay (minutes) | 15 - 10,080 | 15 - 10,080 | 15 - 10,080 | 15 - 10,080 | 15 - 10,080 |
 | Columnstore support | Yes <sup>1</sup> | Yes | Yes | Yes | Yes |
 | In-memory OLTP storage (GB) | N/A | N/A | N/A | N/A | N/A |
 | Max data size (GB) | 512 | 1024 | 1024 | 1024 | 2048 |
@@ -109,7 +109,7 @@ The following table covers these SLOs: `GP_S_Gen5_10`, `GP_S_Gen5_12`, `GP_S_Gen
 |:-|-:|-:|-:|-:|-:|
 | Hardware | Gen5 | Gen5 | Gen5 | Gen5 | Gen5 |
 | Min-max memory (GB) | 3.75-30 | 4.50-36 | 5.25-42 | 6.00-48 | 6.75-54 |
-| Min-max auto-pause delay (minutes) | 60-10,080 | 60-10,080 | 60-10,080 | 60-10,080 | 60-10,080 |
+| Min-max auto-pause delay (minutes) | 15-10,080 | 15-10,080 | 15-10,080 | 15-10,080 | 15-10,080 |
 | Columnstore support | Yes | Yes | Yes | Yes | Yes |
 | In-memory OLTP storage (GB) | N/A | N/A | N/A | N/A | N/A |
 | Max data size (GB) | 2048 | 3072 | 3072 | 3072 | 3072 |
@@ -145,7 +145,7 @@ The following table covers these SLOs: `GP_S_Gen5_20`, `GP_S_Gen5_24`, `GP_S_Gen
 |:-|-:|-:|-:|-:|-:|
 | Hardware | Gen5 | Gen5 | Gen5 | Gen5 | Gen5 |
 | Min-max memory (GB) | 7.5-60 | 9-72 | 12-96 | 15-120 | 30-240 |
-| Min-max auto-pause delay (minutes) | 60-10,080 | 60-10,080 | 60-10,080 | 60-10,080 | 60-10,080 |
+| Min-max auto-pause delay (minutes) | 15-10,080 | 15-10,080 | 15-10,080 | 15-10,080 | 15-10,080 |
 | Columnstore support | Yes | Yes | Yes | Yes | Yes |
 | In-memory OLTP storage (GB) | N/A | N/A | N/A | N/A | N/A |
 | Max data size (GB) | 3072 | 4096 | 4096 | 4096 | 4096 |