You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
:::image type="content" source="media/active-geo-replication-configure-portal/azure-cli-create-geo-replica.png" alt-text="Screenshot that shows the Configure geo-replication option.":::
46
46
47
47
3. Select or create the server for the secondary database, and configure the **Compute + storage** options if necessary. You can select any region for your secondary server, but we recommend the [paired region](/azure/availability-zones/cross-region-replication-azure).
:::image type="content" source="media/active-geo-replication-configure-portal/azure-portal-create-and-configure-replica.png" alt-text="Screenshot that shows the Create and configure replica screen." lightbox="media/active-geo-replication-configure-portal/azure-portal-create-and-configure-replica.png":::
50
50
51
51
Optionally, you can add a secondary database to an elastic pool. To create the secondary database in a pool, select **Yes** next to **Want to use SQL elastic pool?** and select a pool on the target server. A pool must already exist on the target server. This workflow doesn't create a pool.
52
52
53
53
4. Click **Review + create**, review the information, and then click **Create**.
54
54
55
55
5. The secondary database is created and the deployment process begins.
56
56
57
-
:::image type="content" source="./media/active-geo-replication-configure-portal/azure-portal-geo-replica-deployment.png" alt-text="Screenshot that shows the deployment status of the secondary database.":::
57
+
:::image type="content" source="media/active-geo-replication-configure-portal/azure-portal-geo-replica-deployment.png" alt-text="Screenshot that shows the deployment status of the secondary database." lightbox="media/active-geo-replication-configure-portal/azure-portal-geo-replica-deployment.png":::
58
58
59
59
6. When the deployment is complete, the secondary database displays its status.
60
60
61
-
:::image type="content" source="./media/active-geo-replication-configure-portal/azure-portal-sql-database-secondary-status.png" alt-text="Screenshot that shows the secondary database status after deployment.":::
61
+
:::image type="content" source="media/active-geo-replication-configure-portal/azure-portal-sql-database-secondary-status.png" alt-text="Screenshot that shows the secondary database status after deployment." lightbox="media/active-geo-replication-configure-portal/azure-portal-sql-database-secondary-status.png":::
62
62
63
63
7. Return to the primary database page, and then select **Replicas**. Your secondary database is listed under **Geo replicas**.
64
64
65
-
:::image type="content" source="./media/active-geo-replication-configure-portal/azure-sql-db-geo-replica-list.png" alt-text="Screenshot that shows the SQL database primary and geo replicas.":::
65
+
:::image type="content" source="media/active-geo-replication-configure-portal/azure-sql-db-geo-replica-list.png" alt-text="Screenshot that shows the SQL database primary and geo replicas.":::
66
66
67
67
# [Azure CLI](#tab/azure-cli)
68
68
@@ -152,7 +152,7 @@ The secondary database can be switched to become the primary.
152
152
2. Scroll to **Data management**, and then select **Replicas**.
153
153
3. In the **Geo replicas** list, select the database you want to become the new primary, select the ellipsis, and then select **Forced failover**.
154
154
155
-
:::image type="content" source="./media/active-geo-replication-configure-portal/azure-portal-select-forced-failover.png" alt-text="Screenshot that shows selecting forced failover from the drop-down.":::
155
+
:::image type="content" source="media/active-geo-replication-configure-portal/azure-portal-select-forced-failover.png" alt-text="Screenshot that shows selecting forced failover from the drop-down." lightbox="media/active-geo-replication-configure-portal/azure-portal-select-forced-failover.png":::
Copy file name to clipboardExpand all lines: azure-sql/database/doc-changes-updates-release-notes-whats-new.md
+9-2Lines changed: 9 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -5,7 +5,7 @@ description: Learn about the new features and documentation improvements for Azu
5
5
author: WilliamDAssafMSFT
6
6
ms.author: wiassaf
7
7
ms.reviewer: mathoma, randolphwest
8
-
ms.date: 10/30/2023
8
+
ms.date: 11/06/2023
9
9
ms.service: sql-database
10
10
ms.subservice: service-overview
11
11
ms.topic: whats-new
@@ -40,7 +40,7 @@ The following table lists the features of Azure SQL Database that are currently
40
40
|[Azure SQL triggers for Azure Functions](/azure/azure-functions/functions-bindings-azure-sql-trigger)| Azure Functions supports function triggers for the Azure SQL and SQL Server products. |
41
41
|[DC-series hardware up to 40 vCores](resource-limits-vcore-single-databases.md)| DC-series hardware from 10 to 40 vCores is now in preview for in General Purpose, Business Critical, and Hyperscale provisioned compute. |
42
42
|[Degrees of Parallelism (DOP) feedback](/sql/relational-databases/performance/intelligent-query-processing-feedback#degree-of-parallelism-dop-feedback)| DOP Feedback is currently available as a limited preview. For more information and how to apply for the preview, see [Announcing Degree of Parallelism Feedback Limited Preview](https://techcommunity.microsoft.com/t5/azure-sql-blog/announcing-degree-of-parallelism-feedback-limited-preview/ba-p/3806924). |
43
-
|[Elastic jobs](elastic-jobs-overview.md)|The elastic jobs feature is the SQL Server Agent replacement for Azure SQL Database as a PaaS offering. |
43
+
|[Elastic jobs](elastic-jobs-overview.md)|Updated with a preview refresh and new capabilities in November 2023, elastic jobs are the SQL Server Agent replacement for Azure SQL Database. Elastic jobs now support Microsoft Entra (formerly Azure Active Directory) authentication, Azure Private links, management via REST APIs, Azure Alerts, and new capabilities and user interface in the Azure portal. Job Agents now provide four capacity tiers to scale concurrency for job execution. |
44
44
|[Elastic queries](elastic-query-overview.md)| The elastic queries feature allows for cross-database queries in Azure SQL Database. |
45
45
|[Elastic transactions](elastic-transactions-overview.md)| Elastic transactions allow you to execute transactions distributed among cloud databases in Azure SQL Database. |
46
46
|[Free Azure SQL Database](free-offer.md)| Try Azure SQL Database for free, for the life of your subscription. This free offer provides a General Purpose database with 100,000 vCore seconds of compute every month. |
@@ -84,6 +84,13 @@ The following table lists the new generally available (GA) features of Azure SQL
84
84
85
85
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).
86
86
87
+
### November 2023
88
+
89
+
| Changes | Details |
90
+
| --- | --- |
91
+
|**Elastic jobs (preview)**| The [elastic jobs](elastic-jobs-overview.md) feature is the SQL Server Agent replacement for Azure SQL Database. New features and documentation enhancements have been added in a preview refresh in November 2023. Elastic jobs now support Microsoft Entra (formerly Azure Active Directory) authentication, Private links, management via REST APIs, Azure Alerts, and new capabilities and user interface in the Azure portal. Job Agents now provide four capacity tiers to scale concurrency for job execution. |
0 commit comments