[logs] Database logging

[Paul Melson]

On 8/3/07, James B Horwath <Jim_Horwath at glic.com> wrote:
> I have an interest in database logging.  For how important securing and
> logging database access should be, it is not a hot topic of discussion.
> Does anyone have any database logging experience with products or
> methodology they would be willing to share with the list?  I would be
> interested in any benefit or risk for a particular technology or vendor
> solution.  Thanks in advance.

He won't likely say so on list, but I will cuz I don't work for or
with him or even use his product, so this truly isn't a shill.  Anton
wrote a paper that is probably the best single source I've encountered
for those considering database logging.  I'm confident that if you
asked him he would share a copy with you, or if you're a CSI member
you already have access to it that way.

My $0.02 is that database logging kinda sucks because 1) it has very
real performance implications and 2) most databases don't log all of
the interesting stuff to a single location.  There's probably value
there for you in terms of the application visibility this will grant
you, but it will also be something of an effort.  (As opposed to
syslog which also sucks, but is easy to do. :-)

PaulM