2 suggestions for DBMonitor
Posted: Thu 21 Jul 2011 21:57
Hello,
I don't know if this is the right forum for DBMonitor. If not, please move this posting.
Since I use UniDAC, DBMonitor is one of my favorite debugging tools. It's great but I think, you can make it a little better. Please note my two suggestions:
1. It would be helpful if DBMonitor writes the complete error message into the logfile. Sometimes users send logfiles, but it's no help. For example DBMonitor shows
But the logfile contains only
2. I don't know whether you have noticed my suggestion in my post a few days ago. So I write it here again: It will be helpful when DBMonitor shows traffic from TUniMetadata.
Please take this on your to-do list. Maybe you can realize it in one of next versions of DBMonitor.
Kind regards,
Gerd Brinkmann
invent GmbH
I don't know if this is the right forum for DBMonitor. If not, please move this posting.
Since I use UniDAC, DBMonitor is one of my favorite debugging tools. It's great but I think, you can make it a little better. Please note my two suggestions:
1. It would be helpful if DBMonitor writes the complete error message into the logfile. Sometimes users send logfiles, but it's no help. For example DBMonitor shows
Code: Select all
select * from xyz
Dynamic SQL Error
SQL error code = -204
Table unknown
XYZ
Code: Select all
21.07.2011 23:27:50 0,172 SQL Execute: select * from xyz
Error
2. I don't know whether you have noticed my suggestion in my post a few days ago. So I write it here again: It will be helpful when DBMonitor shows traffic from TUniMetadata.
Please take this on your to-do list. Maybe you can realize it in one of next versions of DBMonitor.
Kind regards,
Gerd Brinkmann
invent GmbH