Skip to content

Commit a9f99df

Browse files
authored
Merge pull request #241187 from Clare-Zheng82/0612-Update_mvnet_pricing_doc
[Doc update] - Update MVnet pricing doc
2 parents d71d635 + a2fe07d commit a9f99df

File tree

2 files changed

+4
-4
lines changed

2 files changed

+4
-4
lines changed
-5.01 KB
Loading

articles/data-factory/pricing-examples-data-integration-managed-vnet.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -7,7 +7,7 @@ ms.reviewer: jburchel
77
ms.service: data-factory
88
ms.subservice: pricing
99
ms.topic: conceptual
10-
ms.date: 09/22/2022
10+
ms.date: 06/12/2023
1111
---
1212

1313
# Pricing example: Data integration in Azure Data Factory Managed VNET
@@ -34,12 +34,12 @@ To accomplish the scenario, you need to create two pipelines with the following
3434
| **Operations** | **Types and Units** |
3535
| --- | --- |
3636
| Run Pipeline | 6 Activity runs **per execution** (2 for trigger runs, 4 for activity runs) = 1440, rounded up since the calculator only allows increments of 1000.|
37-
| Execute Delete Activity: pipeline execution time **per execution** = 7 min. If the Delete Activity execution in the first pipeline is from 10:00 AM UTC to 10:05 AM UTC and the Delete Activity execution in second pipeline is from 10:02 AM UTC to 10:07 AM UTC. | Total 7 min / 60 min \* 240 montly executions = 28 pipeline activity execution hours in Managed VNET. Pipeline activity supports up to 50 concurrent executions in Managed VNET. There's a 60 minutes Time To Live (TTL) for pipeline activity. |
38-
| Copy Data Assumption: DIU execution time **per execution** = 10 min if the Copy execution in first pipeline is from 10:06 AM UTC to 10:15 AM UTC and the Copy Activity execution in second pipeline is from 10:08 AM UTC to 10:17 AM UTC. | 10 min \ 60 min * 4 Azure Integration Runtime (default DIU setting = 4) For more information on data integration units and optimizing copy performance, see [this article](copy-activity-performance.md) |
37+
| Execute Delete Activity: pipeline execution time **per execution** = 7 min. If the Delete Activity execution in the first pipeline is from 10:00 AM UTC to 10:05 AM UTC and the Delete Activity execution in second pipeline is from 10:02 AM UTC to 10:07 AM UTC. | Total (7 min + 60 min) / 60 min * 30 monthly executions = 33.5 pipeline activity execution hours in Managed VNET. Pipeline activity supports up to 50 concurrent executions in Managed VNET. There's a 60 minutes Time To Live (TTL) for pipeline activity. |
38+
| Copy Data Assumption: DIU execution time **per execution** = 10 min if the Copy execution in first pipeline is from 10:06 AM UTC to 10:15 AM UTC and the Copy Activity execution in second pipeline is from 10:08 AM UTC to 10:17 AM UTC.| [(10 min + 2 min (queue time charges up to 2 minutes)) / 60 min * 4 Azure Managed VNET Integration Runtime (default DIU setting = 4)] * 2 = 1.6 daily data movement activity execution hours in Managed VNET. For more information on data integration units and optimizing copy performance, see [this article](copy-activity-performance.md) |
3939

4040
## Pricing calculator example
4141

42-
**Total scenario pricing for 30 days: $42.14**
42+
**Total scenario pricing for 30 days: $83.50**
4343

4444
:::image type="content" source="media/pricing-concepts/scenario-5-pricing-calculator.png" alt-text="Screenshot of the pricing calculator configured for data integration with Managed VNET." lightbox="media/pricing-concepts/scenario-5-pricing-calculator.png":::
4545

0 commit comments

Comments
 (0)