Is use of dbms_output fine on production environments?
TanyMay 24 2012 — edited May 29 2012Hi!
I use dbms_output built-in package for debugging messages whenever I write a package/procedure etc., so that I know WHICH PART of code is creating problem.
But in my organization, it is not appreciated on the production environment and on code maintenance tools.
So, I wanted to know if it is an industry practice to not to include dbms_output package in the code? And if it is so, then why ?
In my opinion, if we let it remain there, we are enabling code maintenance by helping the bug-fixer (if required in future) to find the problematic part of code within hundreds/thousands of line of code.
Thanks for your help.
Greatly appreciated.