I have 2 SQL Server databases, `Parent` and `Child`. Both are not always in the same server, but there is always a reference to `Parent` in the `Child` database using linked server. `Child` database makes changes to `Parent` database through stored procedures and synonyms, so both databases always are in the same 'state'. 

The problem is that sometimes a client of my system makes a backup of only one of this databases, make some changes (that affects both databases), and then restore this backup. In that moment, both databases are not in the same 'state'.

I would like to know if this is happening, so when a user open the software using the `Child` database, I can show an error message.

I thought about setting up a Job, writing some kind of version number of both databases every `n` seconds, but this doesn't work, because this version number is base on time, not in changes made to the databases. 

I was thinking too about a version number based on the replication log of the database, but I don't know much about the subject.