We have been using database for our logging (using the log4j) for the past two years and the debugging, Root cause analysis was just awesome along with generating Analytics of our calling channel traffic etc. The disadvantage in our scenario was, the SQL job (DB owned by DBA team) that was created to purge the database used to fail very often because running out of buffer space and the recovery of that job was pretty messy on the IS side (since the DB was in a hung state) and there were stale connections.
Recently a decision was made to switch back logging to File system (which we had earlier) as in our case the cons outweighed the pros with DB logging.
From my experiences my advice would be, unless you have complete control over the database/schema and there are no other teams (non WM) trying to control what you do to it, DB logging will work great. If you do not have the luxury of that, then i would suggest stick to File logging.
Cheers,
Akshith
#webMethods#webMethods-General#Integration-Server-and-ESB#webMethods-Architecture