Instead of logging to the database, it could make more sense to log to the operating system.
- The OS has already a great way of maintaining logs, so there isn’t really any need to have a separated database logging.
- The options to maintain or report logs with the OS are much larger than the default Drupal database logging system.
- Database logging eats away performance from your server, certainly when Drupal writes tons of logfiles each day.
- Any shared hosted website can’t use this option, because they have no access to the OS’ logsystem.
- If your website is maintained by a so called “webmaster” or a “not so technically equipped person”, it may be easier to log to the database, because nontech persons would generally prefer to access the logs through the Drupal admin interface instead of using some dodgy Unix command. Of course, you could ask yourself if a nontech person is anything with the Drupal logs in the first place.