Organization: Silicon Graphics, Inc., Mountain View, CA, USA
Lines: 28
Nntp-Posting-Host: bondo.corp.sgi.com
In article <28244@sybase.sybase.com>, skumar@sybase.com (Shiva Kumar) writes:
|> Sybase log formats are SYBASE CONFIDENTIAL. As far as the auit trail feature
|> goes it is rumoured it would be a part of the SYSTEM 10 release.
|>
|>
|> Thankx
|>
|> Siva
What Siva and others in Sybase technical support use, at least in release 4.2 and previous, is the "DBCC LOG" command, which prints out formatted log records for analysis.
Why this command is not available to users is a _mystery_ to me. It is extraordinarily useful for analysis of the update behavior of application SQL -
(what? inserting 10 rows causes HOW MUCH physical IO? WHY?) - somehing that every Sybase database administrator in the land ought to have access to.
(saw/heard on the phone a Sybase/SQL Solutions technical rep "perform" this command once, a long while ago... I put the command into my notebook for future use!)
This group ought to demand to Sybase that "dbcc log", and any other benign technique that might by highly useful to the user community, be published for general use. It does not matter whether Sybase log formats are confidential or not, and frankly the log format should be of no concern to the user. What does matter is that we are able to report on log contents, for problem analysis.
BTW the transaction log would not be very useful for auditing a user. It shows
what data pages were changed and what physical commands happened to change them, but not necessarily what happened logically.
