Skip to main content

[1] Azure Tips and Tricks: SQL migration to Azure with near-zero downtime

Context:

You need to do a migration from an on-premises SQL Server 2019 instance to Microsoft Azure. There are 3 databases that need to be migrated, each of them has around 3-4 TB. The migration plan includes an Azure SQL Database Managed Instances.

Problem:

The challenges are around the data loss during migration and how to minimize the downtime. 


Solution

The first thing that you need to do is to include DMA (Database Migration Assistant) during the migration assessment. It would allow you to identify any compatibility issues between on-premises and Azure. Additional, DMA is able to provide a list of actions that can be done on the destination environments to do reliability and performance improvements. 

The migration of the schema, data, and uncontained objects can be done using DMA. Allowing to have a migration plan with near-zero downtime. 

On top of it is mandatory to consider DAG (Distributed Availability Groups) for the managed instances, which would enable you to have a strong DR (Disaster Recovery) plan. Think twice if you really need DAG versus the out of the shelve backup and replication capabilities offered by SQL in Azure.

At this moment in time configuration of DAG is done only from the command line and you need to be well documented. Why? Because it involves creating WSFC clusters, AG (Availability Groups) for each WSFC, an ILB (Internal Load Balancer), and configure in the write way the AG endpoint (port 5022 for SQ). Don't forget about port 1433 and 5022 that needs to be available between the clusters. 

The documentation is pretty well, but with testing, it will require you 2MD for the full configuration and testing of DAG.


Comments

Popular posts from this blog

How to audit an Azure Cosmos DB

In this post, we will talk about how we can audit an Azure Cosmos DB database. Before jumping into the problem let us define the business requirement: As an Administrator I want to be able to audit all changes that were done to specific collection inside my Azure Cosmos DB. The requirement is simple, but can be a little tricky to implement fully. First of all when you are using Azure Cosmos DB or any other storage solution there are 99% odds that you’ll have more than one system that writes data to it. This means that you have or not have control on the systems that are doing any create/update/delete operations. Solution 1: Diagnostic Logs Cosmos DB allows us activate diagnostics logs and stream the output a storage account for achieving to other systems like Event Hub or Log Analytics. This would allow us to have information related to who, when, what, response code and how the access operation to our Cosmos DB was done. Beside this there is a field that specifies what was th...

Can User Technical Profile Influence AI Architecture Decisions?

In the last few days, I ran a small experiment on Devin/Windsurf/Cascade, BMAD, and LLM-based architecture decisions. The initial concern was simple: if an AI coding assistant knows something about the user, for example, that the user is a Java developer or a .NET developer, can this information influence the architecture and technology stack that the AI will propose? This question is important because many companies are starting to use AI tools not only for coding but also for product discovery, architecture, documentation, and technical decision-making. If the AI is influenced by the developer's personal profile, the result may not be fully neutral. It may look like a business or architecture decision, but in reality, it may be partially shaped by the context of the person using the tool. The test was done using BMAD with Devin/Windsurf/Cascade. The scenario was a unified field service operations platform. The task was to let BMAD refine the product, define the architecture and s...

ADO.NET provider with invariant name 'System.Data.SqlClient' could not be loaded

Today blog post will be started with the following error when running DB tests on the CI machine: threw exception: System.InvalidOperationException: The Entity Framework provider type 'System.Data.Entity.SqlServer.SqlProviderServices, EntityFramework.SqlServer' registered in the application config file for the ADO.NET provider with invariant name 'System.Data.SqlClient' could not be loaded. Make sure that the assembly-qualified name is used and that the assembly is available to the running application. See http://go.microsoft.com/fwlink/?LinkId=260882 for more information. at System.Data.Entity.Infrastructure.DependencyResolution.ProviderServicesFactory.GetInstance(String providerTypeName, String providerInvariantName) This error happened only on the Continuous Integration machine. On the devs machines, everything has fine. The classic problem – on my machine it’s working. The CI has the following configuration: TeamCity .NET 4.51 EF 6.0.2 VS2013 It see...