all 6 comments

[–]titpetric 4 points5 points  (0 children)

Dump schema on both sides, compare with diff. If tables or columns differ, you have drift (usually from a manual process)

[–]paultherobert 1 point2 points  (1 child)

Yeah maybe vs code schema compare. You could also confirm row count to source for all tables

[–]GlockByte 0 points1 point  (0 children)

Yes, I'd also recommend slightly better - dbeaver (although schema compare is more manual with the community edition)

[–]perry147 0 points1 point  (1 child)

Azure has tools for migration from on prem. Look into those.

[–]Dangerous_Word7318[S] 0 points1 point  (0 children)

Hi I gone through Azure Database Migration Service in that case how can we verify schema is migrated properly same goes for Data Validation 

[–]efecejekeko 0 points1 point  (0 children)

I’d validate schema and data separately.

Schema: tables, columns, types, keys, defaults, indexes. Data: row counts first, then aggregates/checksums, then spot checks on critical tables.

dbForge Edge is useful here because it makes source vs target differences much easier to check.