Eg2 in MySQL, depending on the table engine used, you can choose between Restrict (same behaviour as Oracle), Cascade (deleting records from a table will also automatically delete any records that reference it), or Update (deleting records from a table will update the records that reference that data, setting the foreign key to NULL). This, too, is all inbuilt and doesn’t require any specific application-level relationship validation, or any kind of assessment. They’re standard features.

Of course, this all assumes you’ve set up your foreign key relationships correctly. If you haven’t, you’re doing it wrong. If your RDBMS doesn’t support relationships, you’re doing it wrong. In these cases, performing your assessment is the least of your worries.
References :

How can we support you without a model view of the environment around your table??

References :