Skip to content

Latest commit

 

History

History
38 lines (23 loc) · 2.7 KB

File metadata and controls

38 lines (23 loc) · 2.7 KB

Azure CosmosDB Data Transfer Service Private Preview Tutorials

This book contains tutorials that demo how to use data transfer service to export and import of data from Azure CosmosDB Cassandra API using Azure Storage using Managed Identity.

Prerequisites

To start tutorials, you would need to have Azure Subscription with 'Data Transfer Capability', if you don't have one, please email shwetn@microsoft.com and skarri@microsoft.com with your subscription id.

Note: There is a charge associated with this service and shows up on your invoice as 'Cluster compute', if you have more billing questions which will be addressed in the email.

If you don't have an Azure subscription, create a free account before you begin.

Tools

  • Azure Studio (Note: Samples use Powershell and Python 3 kernals, please ensure these kernal dependencies are installed before running the samples)

Azure Resources

  • Azure CosmosDB Cassandra API Account, if you don't have one Create a free account

  • Azure Storage Account, if you don't have one click here

  • Azure Cosmos DB Cassandra API Table, if you don't have one, please use this notebook to setup sample data

Enable Managed Idendtity between Azure CosmosDB Account and Azure Storage Account

  • Data transfer uses Managed Identity to access Azure storage account. This is required for enteprise security and to avoid keys. please click here and complete this setup.

Provision a Data Transfer Service Cluster

  • please click here and complete this before tyring export and import. Data transfer service uses this cluster to perform export and import operations.

Export/Import data between Azure CosmosDB Cassandra Account and Azure Storage

  • please click here and follow instructions in the notebook.

Usecases

  • Migrate table from shared throughput to dedicated throughput vice versa.
  • Change partition key (Note: Schema of the Source and Destination must be same).
  • Migrate table with more rus to smaller rus to reduce foot print underneath it.
  • Longer retention backups in Avro format for auditing purpose.