Muokkaa

Jaa


Pricing example: Copy data and transform it with Azure Databricks

APPLIES TO: Azure Data Factory Azure Synapse Analytics

Tip

Try out Data Factory in Microsoft Fabric, an all-in-one analytics solution for enterprises. Microsoft Fabric covers everything from data movement to data science, real-time analytics, business intelligence, and reporting. Learn how to start a new trial for free!

In this scenario, you want to copy data from AWS S3 to Azure Blob storage and transform the data with Azure Databricks on an hourly schedule for 8 hours per day for 30 days.

The prices used in this example below are hypothetical and aren't intended to imply exact actual pricing. Read/write and monitoring costs aren't shown since they're typically negligible and do not impact overall costs significantly. Activity runs are also rounded to the nearest 1000 in pricing calculator estimates.

Note

This estimate is for Azure Data Factory costs involved only. Azure Databricks will also incur costs in this scenario, however, which you can estimate using the Azure Pricing Calculator.

Refer to the Azure Pricing Calculator for more specific scenarios and to estimate your future costs to use the service.

Configuration

To accomplish the scenario, you need to create a pipeline with the following items:

  • One copy activity with an input dataset for the data to be copied from AWS S3, and an output dataset for the data on Azure storage.
  • One Azure Databricks activity for the data transformation.
  • One schedule trigger to execute the pipeline every hour. When you want to run a pipeline, you can either trigger it immediately or schedule it. In addition to the pipeline itself, each trigger instance counts as a single Activity run.

Diagram shows a pipeline with a schedule trigger. In the pipeline, copy activity flows to an input dataset, an output dataset, and a DataBricks activity, which runs on Azure Databricks. The input dataset flows to an AWS S3 linked service. The output dataset flows to an Azure Storage linked service.

Costs estimation

Operations Types and Units
Run Pipeline 3 Activity runs per execution (1 for trigger run, 2 for activity runs) = 720 activity runs, rounded up since the calculator only allows increments of 1000.
Copy Data Assumption: DIU hours per execution = 10 min 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
Execute Databricks activity Assumption: external execution hours per execution = 10 min 10 min \ 60 min External Pipeline Activity Execution

Pricing calculator example

Total scenario pricing for 30 days: $41.01

Screenshot of the pricing calculator configured for a copy data and transform with Azure Databricks scenario.