Sql Server - Avoid deferred compilation

Question

I have an application that queries and updates two databases at the same time (different from each other) and it has already around 10 to 15 years of usage. So I would like

Answer 1

Please check my answer for the related question here:

I'm looking for a reliable way to verify T-SQL stored procedures. Anybody got one?

I have not checked it with 2 databases, but if worked fine for the objects in my single-database app.

Answer 2

There is no guaranteed way.

Deferred name resolution (as in if a table isn't there, give an error) applies at compile time, not create time. Although there is some evidence to show that code may run with missing tables

It has been requested though: see the proposed SET OPTION STRICT ON MS Connect request which comes from Erland Sommarskog