Disabling SET Statements / Forcing SET Options in SQL Server 2008R2/2012
There is no way to enforce a global setting or prevent people running 

SET ANSI_NULLS OFF
SET ANSI_PADDING OFF


You can get a quick idea if your application is using any deprecated features by running

SELECT *
FROM   sys.dm_os_performance_counters
WHERE  object_name LIKE '%Deprecated%'
       AND cntr_value &gt; 0
ORDER  BY cntr_value DESC 


If you do find areas of concern then you could set up a Server Side trace capturing the deprecation events.



This also returns the session id and SQL Handle of the offending batch to allow you to investigate further if you do see any events.

A slightly more sophisticated approach would be to set up a notification procedure to retrieve the text associated with the SQL Handle more quickly to reduce the probability that the offending SQL is no longer in the cache when you come to analyse the results.

Or you could probably use extended events to retrieve the TSQL along with the event.