[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

Windows Docker Containers can make WIN32 API calls, use COM and ASP.NET WebForms

After the last post , I received two interesting questions related to Docker and Windows. People were interested if we do Win32 API calls from a Docker container and if there is support for COM. WIN32 Support To test calls to WIN32 API, let’s try to populate SYSTEM_INFO class. [StructLayout(LayoutKind.Sequential)] public struct SYSTEM_INFO { public uint dwOemId; public uint dwPageSize; public uint lpMinimumApplicationAddress; public uint lpMaximumApplicationAddress; public uint dwActiveProcessorMask; public uint dwNumberOfProcessors; public uint dwProcessorType; public uint dwAllocationGranularity; public uint dwProcessorLevel; public uint dwProcessorRevision; } ... [DllImport("kernel32")] static extern void GetSystemInfo(ref SYSTEM_INFO pSI); ... SYSTEM_INFO pSI = new SYSTEM_INFO(

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

Navigating Cloud Strategy after Azure Central US Region Outage

Looking back, July 19, 2024, was challenging for customers using Microsoft Azure or Windows machines. Two major outages affected customers using CrowdStrike Falcon or Microsoft Azure computation resources in the Central US. These two outages affected many people and put many businesses on pause for a few hours or even days. The overlap of these two issues was a nightmare for travellers. In addition to blue screens in the airport terminals, they could not get additional information from the airport website, airline personnel, or the support line because they were affected by the outage in the Central US region or the CrowdStrike outage. But what happened in reality? A faulty CrowdStrike update affected Windows computers globally, from airports and healthcare to small businesses, affecting over 8.5m computers. Even if the Falson Sensor software defect was identified and a fix deployed shortly after, the recovery took longer. In parallel with CrowdStrike, Microsoft provided a too

Cloud as a Story - Vunvulea Radu

Search This Blog