I've configured transactional replication on 2 SQL 2014 instances.
Reboots of a server can sometimes cause issues with replication so I'd like to have a fool-proof technique of checking the status every so often.
In the past, I've just compared row counts for 2 heavily-used tables, then send an email alert if the counts don't match OR are off by several rows.
That works fairly well but I'm wondering if I can interrogate anything on the subscriber - repl job status perhaps? to build a better solution.