Check a database structure before a migration or handover
Before moving a database, integrating a new data source, or taking over an unfamiliar project, it helps to understand how its tables fit together. Look for missing relationships, inconsistent columns, duplicate-looking records, and areas that may need a closer review before making changes.
A practical review process
- Load the database information or supported export that this page accepts, and confirm you are reviewing the intended dataset.
- Start with the table and column overview. Check key fields, relationships, empty values, repeated records, and any reported warnings.
- Investigate flagged tables in the source database or export. Record which issues are confirmed and which are only possibilities before changing the schema or data.
Prioritise findings by impact
A table without an obvious relationship may be intentional, and a column with many empty values may be optional. Conversely, a missing key or unexpected duplicate can affect imports and reports. Compare each finding with the application's data rules and ask whether it could cause an actual problem for the work you plan to do.
A static analysis cannot confirm every behaviour of a live database, execute all queries, or prove that an application will work after a migration. Keep a backup, test planned changes in a safe environment, and verify important relationships against the actual schema and data.
Frequently asked questions
Does a clean report guarantee the data or query is correct?
No. The checks help find likely problems, but you still need to verify results against the requirements of the application and the data itself.
Should I keep an unchanged copy?
Yes. Keep the original file or script until the reviewed result has been checked and accepted in the intended workflow.