I agree but that it could be bad and could cause an unexpected result and cost. If "clean up" means we stop using them in any new work we do, that is fine. We clean up our act and code right from now on. However, this topic also brings up the question of should we start to readdress the backlog of code we have in our shop to eliminate the old clunky way of doing things? This would be sort of a clandestine effort to make it better SQL and conform to the technical standard newly put in place by us. If you answer yes to that you might want at minimum to speak with your boss before you start addressing code that is working in production.

Now if you want to define a project, where you address conversions of old functions in production code with anticipated risks stated and understood, and your management buying into it before you get underway, you might be far better off.

Also if you adopt a strategy that when you are addressing a problem or enhancing certain functions that at that time you address the silly old functions problem and make it more standard, that also would be a good idea.

Just don't go off into an adventure on your own to make it work the way you want without approval of management, and them understanding what you are doing, the value, and the risks.

M...