We are re-evaluating the functionality contained in dbconsole and we'd like your input. Any thoughts you'd be willing to share would be most welcome. In particular we're interested in:
To get the discussion going, here are a few areas where we could add functionality:
Let me know if any of these seem useful or not.
Thanks for any input you can share.
asked 16 Oct '13, 16:53
I like dbconsole, but I don't use it :)... instead, I look at its feature set from time to time to see if anything should be added to Foxhound. Some stuff I take, and other stuff I leave alone because Sybase Central and/or ISQL also do it, and Foxhound is primarily a passive monitor.
Clients use dbconsole a lot on engines started as services, as a system tray icon alternative.
If browser-based, then make sure it works on tablets... so very many websites have only two display modes: workstation versus smartwatch.
answered 17 Oct '13, 08:45
I would like to see its functions being added to Sybase Central. So that you don't need 2 tools.
Dream: Let the tool connect to a database server which is not accepting any standard connections. (this would probably mean to create a second purely administrative connection mechanism)
answered 17 Oct '13, 04:28
I use dbconsole regulary. My expierience is mostly based on sa10 Version
Your Proposals To get the discussion going, here are a few areas where we could add functionality:
Hope i could give some ideas. Would be glad to give more details if necessary.
Setting the font to a monospaced font for messages would be nice (possible in Linux because of the OS) Setting the tab size would also be nice - generally use 4 instead of 8.
answered 28 Oct '13, 11:41
FWIW, I don't use DBCONSOLE at all (I guess I stopped using a separate DB monitor after using DBWATCH v5.5:) - my database servers always do use -o, so the console output is available as text file (and I'm using MESSAGEs quite often within procedures and the like...). - When I do need to access the console log immediately, I do use a particular stored procedure (called "STP_ShowLastLogMessages()") that uses the builtin properties like "MessageText" to list the last n messages. (BTW: That old answer shows that procedure - though MessageText and the related properties have been deprecated now...)
To view connections and users (and locks, though that has only rarely been an issue here), I use DBISQL (or mostly still dbisqlc) with sa_conn_info() and the like.
That is still enough for my needs - somewhat I don't like "heavy UI consoles" to monitor these database servers.
Just my two cents, apparently.
A late remark:
So the new SQL Anywhere Cockpit - introduced in v17 - is the primary answer to that poll?
To cite from the v17 "What's New" setion: