Nitish Anand Srivastava·Jun 3Post 10: Handling Schema Evolution Mid-Migration: Managing Live DDL Changes over Change Data…You are in week three of a live replication catch-up phase, syncing a 40TB database footprint. Suddenly, an automated CI/CD pipeline pushes…
Nitish Anand Srivastava·Jun 3Post 9: Architecture of a 40TB Live Replication Pipeline: Managing CDC Catch-Up PressureSeeding a 40TB database into the cloud is a static engineering challenge. Keeping it synchronized under a live production load of 4,000…
Nitish Anand Srivastava·Jun 1Post 8: Configuring Azure DMS for 40TB SQL Server → Hyperscale: The Full Technical SetupAzure Database Migration Service (DMS) documentation covers the basic configuration wizard. Here is what it completely leaves out when you…
Nitish Anand Srivastava·Jun 1Post 7: All SQL Server Migration Paths to Azure - The Ultimate Decision TreeThere are 7 ways to migrate SQL Server to the cloud. Only 2 are structurally viable when you are moving a 40TB+ production footprint with a…
Nitish Anand Srivastava·May 17Post 6: Restoring 40TB SQL Backup into Azure SQL Hyperscale: Options, Gotchas, and What We…You have 38TB of SQL Server backup files sitting in Azure Blob Storage. Now what?
Nitish Anand Srivastava·May 16Post 5: Azure Data Box for 40TB SQL Server Backup: The Complete PlaybookShipping a physical device with 40TB of your production data across the country sounds risky. Here’s why it’s actually the safest option.
Nitish Anand Srivastava·May 16Post 4: Network Architecture for Zero-Impact Migration: ExpressRoute vs VPN vs Public EndpointYour data transfer strategy is only as good as your network architecture. We made this mistake once. Never again.
Nitish Anand Srivastava·May 14Post 3: Sizing Azure SQL Hyperscale for a 40TB Workload: The Math Behind the DecisionYou can’t right-size a cloud database by gut feel. Here’s the exact methodology we used.
Nitish Anand Srivastava·May 13Post 2: The Discovery Phase Nobody Does Properly: SQL Server Migration EditionMost migrations fail in production because the assessment was done in a spreadsheet. Ours wasn’t.
Nitish Anand Srivastava·May 13Post 1: Why We Chose Azure SQL Hyperscale for a 40TB+ SQL Server MigrationWe had 43TB of SQL Server data on-prem. Moving it to Azure wasn’t just a lift-and-shift. It was a rethink.