| Breck Carter [TeamSybase] 2005-09-11, 8:27 pm |
| It should be possible to capture *all* the various console messages in
the new (Jasper) diagnostic architecture.
This should include the -o output from *all* the db*.exe programs.
Having one single location for capturing all the console outputs would
make some debugging and diagnostic tasks easier. Currently you often
have to try to match up messages written to different files; for
example:
- database server console messages, with dbbackup incremental log
backup messages, with dbbackup live log backup messages (a current
open case involves this kind of study)
- database server and MobiLink server messages
- MobiLink client and MobiLink server messages (perhaps only for test
mode with a limited number of clients)
- the famous four-way: consolidated database - MobiLink server -
MobiLink client - remote database, when various procedures, hooks,
triggers and events put diagnostic messages onto the consolidated and
remote console files.
(Aside: Sometimes the console is the *only* place diagnostic messages
can be sent; e.g., from events, and from any block when dbmlsync is
the client. Other times, it is simply a very convenient, very
*reliable* location for diagnostic output. Also, the MobiLink server
and client console logs are not accessible user-written diagnostics.)
I would imagine parts of this request (dbsrvx and dbbackup) might be
easier to implement than others (dbmlsrvx and dbmlsync)... a phased
implementation is OK with me :)
Breck
--
SQL Anywhere Studio 9 Developer's Guide
Buy the book: http://www.amazon.com/exec/obidos/A...7/risingroad-20
bcarter@risingroad.com
RisingRoad SQL Anywhere and MobiLink Professional Services
www.risingroad.com
|