What kind of techniques everybody is using to debug SQL Stored Procedure. We are using some batch debugging buts its lot of work to trap all the information. Is there any easy way we can debug/troubleshoot SQL Stored Procedure. If SQL Stored procedure happens to fail in production environment is there any way we can trap all the information without hand-coding bunch of insert statement inside SQL Stored Procedure. We are looking at getting as much information as possible like procedure name, location, SQL, SQLCODE, SQLSTATE, If possible data used for failed SQL etc. There is no documentation on debugging techniques on IBM Web site.