As the title of this post indicates, the Database Migration Service (DMS) could experiment with problems in very rare cases with the capacity to start/create a service due to not having enough resources in a specific region. It is interesting to start explaining why the provisioned number of Virtual Machines (VM) could impact DMS. If we ask Why? The answer is simple: behind the scenes, the VMs represent the “workers” in charge of executing ALL the tasks required by the migration service of DMS.

As every option available in Azure and particularly talking about SQL, for the classic question about What option is better for me? The classic answer is still valid and this is “It depends”.  Your necessity or your business workload or architectural design would influence in a determinant way with your decision.

In this article, I am going to explain in a sort of step-by-step guide an approach for configuring a new Azure SQL Managed Instance from now in advance called simply SQL MI.  It is so important to distinguish that exist different ways to arrive at the same result, but the most important is to understand the core concepts.

This is the last article of the series about “Configuring a Cassandra Cluster in the Cloud” composed of three articles, the first article was about the architecture of the Cassandra Cluster and complete prerequisites, in the second article we walked through the setup process for installing Cassandra, and finally, in this article, we will be developing all the steps for completing our solution in Azure.  I would like to highlight that these particular series include Azure as the cloud platform, however, the first two articles can be considered agnostic in terms of the mechanisms and approaches used for the main configuration of the Cassandra Cluster.

This article is the second of the series about configuring a Cassandra Cluster in Azure. In the previous one we completed the installation of Cassandra in a new Virtual Machine (VM) in Azure, this VM will become our template for creating new nodes based on it.  In this article we will be covering the next sections:

• Localize key files
• Configuring our Cluster (cluster name, seed nodes)
• Adding more configuration to Cassandra through yaml file
• Configuring RPC (service, interface, and address)
• Deleting data directory