DBMonitor use with ODAC
Posted: Fri 17 Aug 2012 10:00
Can you improve DBMonitor's use with ODAC? There is no DBMonitor forum so I had no choice but to post it here.
There are some glaringly BAD usability issues in DBMonitor, that make using it a pain for developers and others alike. Each of the following should be easy to implement and add great value to DBMonitor.
1. Add an option to right click on a SQL statement and copy just that statement's information to the clipboard (SQL, Params, Error). Currently you have to save the log, trawl through it, find the statement in question and then copy the information.
2. Format the Params in the log so it is consistent with Oracle SQL and PL/SQL syntax. That way we can simply write an anonymous block and run the offending query without having to spend ages reformatting it!
Currently :
:MANFAC(VARCHAR[2],IN)='KI'
:MODEL(VARCHAR[2],IN)='07'
:TRIMLEVEL_ID(INTEGER,IN)=12771
:RESULT(VARCHAR[3],OUT)=<NULL>
which doesn't help developers in the slightest!
Make it instead :
:MANFAC VARCHAR(2) := 'KI'; -- IN
:MODEL VARCHAR(2) := '07'; --IN
:TRIMLEVEL_ID INTEGER := 12771; -- IN
:RESULT VARCHAR(3) := NULL; -- OUT
This approach should be applied to the Params tab of the current statement as well, whose data columns are also formatted weirdly, and there should be an option to copy these params to the clipboard.
3. Have a "Delete All Inactive" button to remove all inactive processes, rather than having to select one by one.
4. In the Session tree have an entry for "All" which all of the sessions sit under. This then allows us to see all of the statements for the current process. If selecting "All" show a column with the Session name in.
5. An option to select multiple SQL statements and copy to clipboard (either consecutive or particular ones).
To be honest, all of these suggestions are fairly common sense design considerations and should be part of the application by default.
There are some glaringly BAD usability issues in DBMonitor, that make using it a pain for developers and others alike. Each of the following should be easy to implement and add great value to DBMonitor.
1. Add an option to right click on a SQL statement and copy just that statement's information to the clipboard (SQL, Params, Error). Currently you have to save the log, trawl through it, find the statement in question and then copy the information.
2. Format the Params in the log so it is consistent with Oracle SQL and PL/SQL syntax. That way we can simply write an anonymous block and run the offending query without having to spend ages reformatting it!
Currently :
:MANFAC(VARCHAR[2],IN)='KI'
:MODEL(VARCHAR[2],IN)='07'
:TRIMLEVEL_ID(INTEGER,IN)=12771
:RESULT(VARCHAR[3],OUT)=<NULL>
which doesn't help developers in the slightest!
Make it instead :
:MANFAC VARCHAR(2) := 'KI'; -- IN
:MODEL VARCHAR(2) := '07'; --IN
:TRIMLEVEL_ID INTEGER := 12771; -- IN
:RESULT VARCHAR(3) := NULL; -- OUT
This approach should be applied to the Params tab of the current statement as well, whose data columns are also formatted weirdly, and there should be an option to copy these params to the clipboard.
3. Have a "Delete All Inactive" button to remove all inactive processes, rather than having to select one by one.
4. In the Session tree have an entry for "All" which all of the sessions sit under. This then allows us to see all of the statements for the current process. If selecting "All" show a column with the Session name in.
5. An option to select multiple SQL statements and copy to clipboard (either consecutive or particular ones).
To be honest, all of these suggestions are fairly common sense design considerations and should be part of the application by default.