How to Prioritise Testing Activities to Reach Your Goals
summary
Argues that data migration succeeds when teams begin with the end in mind, defining future state, switch‑over dates (example: Windows Server 2012 end‑of‑support 10 Oct 2023), and customer success criteria up front. Lists concrete risks — data loss, corruption, delta loss/duplication, schema drift, integration failures — and prescribes checks: row counts, aggregates, timestamps, CDC, and hashbytes checks. Recommends building parameterized SQL suites (or SSIS packages) so repeatable automated comparisons run reliably by non‑specialists.
AI-written summary · about
chapters (8)
- 0:00Introduction
- 2:36What is Data Migration
- 3:27Why Data Migration
- 4:43Who Matters
- 5:59Common Risks
- 8:20When Testing Begins
- 10:54Questions to Ask
- 14:07Scripting
related talks
18mSolving Migration Pipelines
57mDe-risk Your Azure SQL Migration: 5 Critical Considerations
31mHelp! My Database Is The Bottleneck
50mMigrating data solutions to the cloud - a checklist.
48mMigrating to PostgreSQL: Strategies, Sovereignty, and Success
46mCase study: Users migration testing
28mOrganizational Stability through Reliable Software through Testing
23mChallenges of database testing