I can understand the need to prevent the use in production code, but not in ad-hoc queries when developing and testing (I often use it to evaluate a table structure).
You could have a code review policy and prevent changes to stored procedures, functions and views that won't comply with company standards. You could use tools such as Microsoft SQL Server Data Tools, SQLCop, SQL Code Guard or SQL Enlight to review the code (I couldn't find the right product from Red Gate
, would it be Code Guard?).
Luis C.General Disclaimer:
Are you seriously taking the advice and code from someone from the internet without testing it? Do you at least understand it? Or can it easily kill your server?How to post data/code on a forum to get the best help: Option 1 / Option 2