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
The usage of the [!INCLUDE [ssNoVersion](../../includes/ssnoversion-md.md)] ESU subscription is reported once an hour. The specific meter is automatically selected based on edition and the version eligibel for ESU. The ESU usage will be reported for all v-cores or p-cores visible to the OSE. The following rules apply:
231
+
The usage of the [!INCLUDE [ssNoVersion](../../includes/ssnoversion-md.md)] ESU subscription is reported once an hour. The specific meter is automatically selected based on edition and the version eligible for ESU. The ESU usage will be reported for all v-cores or p-cores visible to the OSE. The following rules apply:
232
232
233
233
- If one or several instances of SQL Server or SQL Server associated services eligible for ESU are installed on a virtual machine and don't specify the use of a p-core ESU license, the ESU subscription usage is metered based on the total number of virtual cores available to the OSE. The minimum is four v-cores per OSE.
234
234
235
235
- If several instances of SQL Server or SQL Server associated services eligible for ESU are installed on a physical server without using virtual machines, the ESU subscription usage is metered based on the total number physical cores available to the OSE. The minimum is four cores per OSE.
236
236
237
-
- If multipe instances of SQL Server or SQL Server associated services are istalled with the same version that is eligible for ESU, only one ESU subscription usage is reported per OSE. The reported usage is adsociated with the instance that has the highest edition.
237
+
- If multiple instances of SQL Server or SQL Server associated services are installed with the same version that is eligible for ESU, only one ESU subscription usage is reported per OSE. The reported usage is associated with the instance that has the highest edition.
238
238
239
-
- If two or more instances of SQL Server or SQL Server associated services are istalled with the different versions that are eligible for ESU, each eligibe version will report ESU usage separately based one the instance of that vesion with teh highets edition. This reflects the differences in ESU prices and bill-back periods for different versions.
239
+
- If two or more instances of SQL Server or SQL Server associated services are installed with the different versions that are eligible for ESU, each eligible version will report ESU usage separately based one the instance of that version with the highest edition. This reflects the differences in ESU prices and bill-back periods for different versions.
240
240
241
241
242
242
The following table shows the ESU subscription meters (also called *SKUs*) that are used for metering and billing for a [!INCLUDE [ssNoVersion](../../includes/ssnoversion-md.md)] ESU subscription on a single OSE:
@@ -321,7 +321,7 @@ If the Arc enabled machine goes offline and reconnects to Azure in a different s
321
321
>
322
322
> This difference is expected, and it should be a one-time charge.
323
323
>
324
-
> During the following months, you should see only the regular hourly charges. Additional bill-back charges could be added in cases of connectivity disruptions, but they're typically much smaller amounts.
324
+
> In following billing periods, you should see only the regular hourly charges. Additional bill-back charges could be added in cases of connectivity disruptions, but they're typically much smaller amounts.
Copy file name to clipboardExpand all lines: docs/sql-server/azure-arc/manage-license-billing.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
@@ -231,9 +231,9 @@ If there are multiple SQL Server instances on the OSE, all instances and replica
231
231
232
232
### Limitations
233
233
234
-
The current passive instance detection logic has the following limitations.
234
+
The current passive instance detection logic has the following limitations:
235
235
236
-
- The checks are done every hour. A failover within the hour may or may not bill both replicas.
236
+
- The checks are hourly. A failover within the hour may or may not bill both replicas.
237
237
- Passive instances for other HADR technologies like log shipping or mirroring are not automatically detected at this time.
238
238
- The detection logic does not support free disaster recovery testing or monitoring connections like database consistency checks, backups or monitoring resource usage data.
239
239
@@ -282,7 +282,7 @@ The usage of the SQL Server software is reported once an hour. The specific mete
282
282
283
283
- If two or more instances of SQL Server or SQL Server associated services are installed on the same OSE the instance with the highest edition will be billed.
284
284
285
-
- The combination of the selected `LicenseType` value and the highest SQL Server edition installed on the OSE defines which meter is sent every hour.
285
+
- The combination of the selected `LicenseType` value and the highest SQL Server edition installed on the OSE defines which meter is sent.
286
286
287
287
For more information, see [SQL Server Licensing Resources and Documents](https://www.microsoft.com/licensing/docs/view/SQL-Server).
0 commit comments