As a DBA, you might get in the situation where someone has disabled a foreign key constraint to insert or delete data, but with enabling the constraint again, the WITH CHECK option wasn't used. Brent Ozar described this situation already a few years ago: https://www.brentozar.com/blitz/foreign-key-trusted/. As he mentioned, the problem is that for these untrusted constraints aren't used in query plans. This usually leads to a major performance impact.
I too had this situation, but then the problem is: how to detect easily of the referential integrity is still in place or not? And if so, how to enable the constraint? Especially if you're working with many tables, it's not easy to resolve this issue. Happily, all the information is stored in system tables, so I wrote a query to create the code to see if the referential integrity is still good, and also code to enable the constraint again with the WITH CHECK. This can then be encapsulated in a loop like a cursor or something.
I created this code for SQL Server 2016. The concatenation I took from the chosen answer in https://stackoverflow.com/questions/194852/how-to-concatenate-text-from-multiple-rows-into-a-single-text-string-in-sql-serv.
Beware: for large tables, enabling the constraint can take quite a while, so execute this part during a time window where locks with a long duration won't mess up other activities (too much).
I hope you like it!