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
Copy file name to clipboardExpand all lines: azure-sql/database/free-offer-faq.yml
+4Lines changed: 4 additions & 0 deletions
Original file line number
Diff line number
Diff line change
@@ -50,6 +50,10 @@ sections:
50
50
answer: |
51
51
Yes, if you change the **Free limit reached behavior** setting to **Continue using for additional charges**.
52
52
53
+
- question: Can I use my Student subscription with the Azure SQL Database free offer database?
54
+
answer: |
55
+
There are multiple student offers. Currently, the Microsoft Azure for Students Starter offer is incompatible with this Azure SQL Database free offer. Instead, consider the [Azure for College Students offer](https://azure.microsoft.com/pricing/offers/ms-azr-0170p/) or the [Azure Free offer](https://azure.microsoft.com/pricing/offers/ms-azr-0044p/). If desired, the **Continue using database for additional charges** option can deduct from the starting credits.
Copy file name to clipboardExpand all lines: azure-sql/database/free-offer.md
+2-1Lines changed: 2 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -4,7 +4,7 @@ description: Guidance on how to deploy the Azure SQL Database free offer for new
4
4
author: NilsPohlmann
5
5
ms.author: nilsp
6
6
ms.reviewer: wiassaf, mathoma, randolphwest
7
-
ms.date: 09/25/2023
7
+
ms.date: 10/10/2023
8
8
ms.service: sql-database
9
9
ms.subservice: service-overview
10
10
ms.topic: how-to
@@ -129,6 +129,7 @@ Compared to a normal General Purpose database, this free offer has the following
129
129
- Elastic Jobs and DNS Alias aren't available for this free offer.
130
130
- The free offer Azure SQL Database can't be a part of an elastic pool or autofailover group.
131
131
- Currently, you can only use the Azure portal to create the free offer database.
132
+
- Currently, the Microsoft Azure for Students Starter offer is incompatible with this Azure SQL Database free offer. Instead, consider the [Azure for College Students offer](https://azure.microsoft.com/pricing/offers/ms-azr-0170p/) or the [Azure Free offer](https://azure.microsoft.com/pricing/offers/ms-azr-0044p/). If desired, the **Continue using database for additional charges** option can deduct from the starting credits.
132
133
- For more information, review the [Azure SQL Database free offer FAQ](free-offer-faq.yml).
Save money with Azure SQL Database or SQL Managed Instance by committing to a reservation for compute resources compared to pay-as-you-go prices. With reserved capacity, you make a commitment for SQL Database and/or SQL Managed Instance use for a period of one or three years to get a significant discount on the compute costs. To purchase reserved capacity, you need to specify the Azure region, deployment type, performance tier, and term.
19
19
20
-
You do not need to assign the reservation to a specific database or managed instance. Matching existing deployments that are already running or ones that are newly deployed automatically get the benefit. Hence, by purchasing a reserved capacity, existing resources infrastructure would not be modified and thus no failover/downtime is triggered on existing resources. By purchasing a reservation, you commit to usage for the compute costs for a period of one or three years. As soon as you buy a reservation, the compute charges that match the reservation attributes are no longer charged at the pay-as-yougo rates.
20
+
You do not need to assign the reservation to a specific database or managed instance. Matching existing deployments that are already running, or ones that are newly deployed automatically, get the benefit. Hence, by purchasing a reserved capacity, existing resources infrastructure would not be modified and thus no failover/downtime is triggered on existing resources. By purchasing a reservation, you commit to usage for the compute costs for a period of one or three years. As soon as you buy a reservation, the compute charges that match the reservation attributes are no longer charged at the pay-as-you-go rates.
21
21
22
-
A reservation applies to both primary and billable secondary compute replicas, but does not cover software, networking, or storage charges associated with the service. At the end of the reservation term, the billing benefit expires and the database or managed instance is billed at the pay-as-yougo price. Reservations do not automatically renew. For pricing information, see the [reserved capacity offering](https://azure.microsoft.com/pricing/details/sql-database/managed/).
22
+
A reservation applies to both primary and billable secondary compute replicas, but does not cover software, networking, or storage charges associated with the service. At the end of the reservation term, the billing benefit expires and the database or managed instance is billed at the pay-as-you-go price. Reservations do not automatically renew. For pricing information, see the [reserved capacity offering](https://azure.microsoft.com/pricing/details/sql-database/managed/).
23
23
24
24
You can buy reserved capacity in the [Azure portal](https://portal.azure.com). Pay for the reservation [up front or with monthly payments](/azure/cost-management-billing/reservations/prepare-buy-reservation). To buy reserved capacity:
25
25
@@ -31,7 +31,7 @@ For more information about how enterprise customers and Pay-As-You-Go customers
31
31
> [!NOTE]
32
32
> Purchasing reserved capacity does not pre-allocate or reserve specific infrastructure resources (virtual machines or nodes) for your use.
33
33
34
-
## Determine correct size before purchase
34
+
## Determine the correct size before purchase
35
35
36
36
The size of reservation should be based on the total amount of compute used by the existing or soon-to-be-deployed database or managed instance within a specific region and using the same performance tier and hardware configuration.
37
37
@@ -56,7 +56,7 @@ Also, let's suppose that you know that you will need these resources for at leas
56
56
57
57
:::image type="content" source="./media/reserved-capacity-overview/sql-reserved-vcores-purchase.png" alt-text="Screenshot before submitting the reserved capacity purchase.":::
58
58
59
-
The following table describes required fields.
59
+
The following table describes the required fields.
Copy file name to clipboardExpand all lines: azure-sql/database/service-tier-hyperscale-replicas.md
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -29,7 +29,7 @@ Each type has a different architecture, feature set, purpose, and cost. Based on
29
29
30
30
## High Availability replica
31
31
32
-
A High Availability (HA) replica uses the same page servers as the primary replica, so no data copy is required to add an HA replica. HA replicas are mainly used to increase database availability; they act as hot standbys for failover purposes. If the primary replica becomes unavailable, failover to one of the existing HA replicas is automatic and quick. Connection string doesn't need to change; during failover applications may experience minimal downtime due to active connections being dropped. As usual for this scenario, proper retry logic is recommended. Several drivers already provide some degree of automatic retry logic. If you are using .NET, the [latest Microsoft.Data.SqlClient](https://devblogs.microsoft.com/azure-sql/configurable-retry-logic-for-microsoft-data-sqlclient/) library provides native full support for configurable automatic retry logic.
32
+
A High Availability (HA) replica uses the same page servers as the primary replica, so no data copy is required to add an HA replica. HA replicas are mainly used to increase database availability; they act as hot standbys for failover purposes. If the primary replica becomes unavailable, failover to one of the existing HA replicas is automatic and quick. The connection string doesn't need to change; during failover applications may experience minimal downtime due to active connections being dropped. As usual for this scenario, proper retry logic is recommended. Several drivers already provide some degree of automatic retry logic. If you are using .NET, the [latest Microsoft.Data.SqlClient](https://devblogs.microsoft.com/azure-sql/configurable-retry-logic-for-microsoft-data-sqlclient/) library provides native full support for configurable automatic retry logic.
33
33
34
34
HA replicas use the same server and database name as the primary replica. Their Service Level Objective is also always the same as for the primary replica. HA replicas are not visible or manageable as a stand-alone resource from the portal or from any API.
35
35
@@ -60,8 +60,8 @@ There are differences between HA replicas and named replicas:
60
60
61
61
As a result, named replicas offer several benefits over HA replicas, for what concern read-only workloads:
62
62
63
-
- Users connected to a named replica will suffer no disconnection if the primary replica is scaled up or down; at the same time, users connected to primary replica will be unaffected by named replicas scaling up or down.
64
-
- Workloads running on any replica, primary or named, will be unaffected by longrunning queries running on other replicas.
63
+
- Users connected to a named replica will suffer no disconnection if the primary replica is scaled up or down; at the same time, users connected to the primary replica will be unaffected by named replicas scaling up or down.
64
+
- Workloads running on any replica, primary or named, will be unaffected by long-running queries running on other replicas.
65
65
66
66
The main goal of named replicas is to enable a broad variety of [read scale-out](read-scale-out.md) scenarios, and to improve Hybrid Transactional and Analytical Processing (HTAP) workloads. Examples of how to create such solutions are available here:
Copy file name to clipboardExpand all lines: azure-sql/database/service-tier-hyperscale.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -107,11 +107,11 @@ The vCore-based service tiers are differentiated based on database availability,
107
107
108
108
| Hardware configuration | CPU | Memory |
109
109
| :--- | :--- | :--- |
110
-
| Standard-series (Gen5) | **Provisioned compute**<br />- Intel® E5-2673 v4 (Broadwell) 2.3 GHz, Intel® SP-8160 (Skylake)<sup>1<sup>, Intel® 8272CL (Cascade Lake) 2.5 GHz<sup>1<sup>, Intel® Xeon Platinum 8307C (Ice Lake)<sup>1<sup>, AMD EPYC 7763v (Milan) processors<br />- Provision up to 128 vCores (hyper-threaded)<br /><br />**Serverless compute**<br />- Intel® E5-2673 v4 (Broadwell) 2.3 GHz, Intel® SP-8160 (Skylake)<sup>1<sup>, Intel® 8272CL (Cascade Lake) 2.5 GHz<sup>1<sup>, Intel Xeon® Platinum 8307C (Ice Lake)<sup>1<sup>, AMD EPYC 7763v (Milan) processors<br />- Autoscale up to 80 vCores (hyper-threaded)<br />- The memory-to-vCore ratio dynamically adapts to memory and CPU usage based on workload demand and can be as high as 24 GB per vCore. For example, at a given point in time, a workload may use and be billed for 240 GB memory and only 10 vCores. | **Provisioned compute**<br />- 5.1 GB per vCore<br />- Provision up to 625 GB<br /><br />**Serverless compute**<br />- Autoscale up to 24 GB per vCore<br />- Autoscale up to 240 GB max |
110
+
| Standard-series (Gen5) | **Provisioned compute**<br />- Intel® E5-2673 v4 (Broadwell) 2.3 GHz, Intel® SP-8160 (Skylake)<sup>1</sup>, Intel® 8272CL (Cascade Lake) 2.5 GHz<sup>1</sup>, Intel® Xeon Platinum 8307C (Ice Lake)<sup>1</sup>, AMD EPYC 7763v (Milan) processors<br />- Provision up to 128 vCores (hyper-threaded)<br /><br />**Serverless compute**<br />- Intel® E5-2673 v4 (Broadwell) 2.3 GHz, Intel® SP-8160 (Skylake)<sup>1</sup>, Intel® 8272CL (Cascade Lake) 2.5 GHz<sup>1</sup>, Intel Xeon® Platinum 8307C (Ice Lake)<sup>1</sup>, AMD EPYC 7763v (Milan) processors<br />- Autoscale up to 80 vCores (hyper-threaded)<br />- The memory-to-vCore ratio dynamically adapts to memory and CPU usage based on workload demand and can be as high as 24 GB per vCore. For example, at a given point in time, a workload may use and be billed for 240 GB memory and only 10 vCores. | **Provisioned compute**<br />- 5.1 GB per vCore<br />- Provision up to 625 GB<br /><br />**Serverless compute**<br />- Autoscale up to 24 GB per vCore<br />- Autoscale up to 240 GB max |
111
111
| Premium-series | - Intel® Xeon Platinum 8307C (Ice Lake), AMD EPYC 7763v (Milan) processors | - 5.1 GB per vCore<br />- Provision up to 128 vCores (hyper-threaded) |
<sup>1<sup> In the [sys.dm_user_db_resource_governance](/sql/relational-databases/system-dynamic-management-views/sys-dm-user-db-resource-governor-azure-sql-database) dynamic management view, hardware generation for databases using Intel® SP-8160 (Skylake) processors appears as Gen6, hardware generation for databases using Intel® 8272CL (Cascade Lake) appears as Gen7, and hardware generation for databases using Intel Xeon® Platinum 8307C (Ice Lake) or AMD® EPYC® 7763v (Milan) appear as Gen8. For a given compute size and hardware configuration, resource limits are the same regardless of CPU type. For more information, see resource limits for [single databases](resource-limits-vcore-single-databases.md) and [elastic pools](resource-limits-vcore-elastic-pools.md).
114
+
<sup>1</sup> In the [sys.dm_user_db_resource_governance](/sql/relational-databases/system-dynamic-management-views/sys-dm-user-db-resource-governor-azure-sql-database) dynamic management view, hardware generation for databases using Intel® SP-8160 (Skylake) processors appears as Gen6, hardware generation for databases using Intel® 8272CL (Cascade Lake) appears as Gen7, and hardware generation for databases using Intel Xeon® Platinum 8307C (Ice Lake) or AMD® EPYC® 7763v (Milan) appear as Gen8. For a given compute size and hardware configuration, resource limits are the same regardless of CPU type. For more information, see resource limits for [single databases](resource-limits-vcore-single-databases.md) and [elastic pools](resource-limits-vcore-elastic-pools.md).
115
115
116
116
Serverless is only supported on Standard-series (Gen5) hardware.
@@ -296,7 +307,20 @@ Replace the following values in the example:
296
307
To get your user-assigned managed identity **Resource ID**, search for **Managed Identities** in the [Azure portal](https://portal.azure.com). Find your managed identity, and go to **Properties**. An example of your UMI **Resource ID** looks like `/subscriptions/<subscriptionId>/resourceGroups/<ResourceGroupName>/providers/Microsoft.ManagedIdentity/userAssignedIdentities/<managedIdentity>`.
0 commit comments