watchdog

Hi

After installing Drupal on Windows 2008 r2, IIS7 and SQL Server 2012, we get errors whenever accessing any of the log pages e.g. under /admin/reports/dblog

gives this error:

PDOException: SQLSTATE[42S02]: [Microsoft][SQL Server Native Client 11.0][SQL Server]Invalid object name 'watchdog'.: SELECT DISTINCT(type) FROM {watchdog} ORDER BY type; Array ( ) in _dblog_get_message_types() (line 133 of C:\inetpub\wwwroot****\modules\dblog\dblog.module).

and under

/admin/reports/access-denied

gives

So supposing you have several sites on D5 that won't get upgraded to D6 (to take advantage of the syslog support) for several months yet due to workload, what are good ways to optimize InnoDB so that Watchdog can write faster, i.e more concurrent INSERT statements, rather than taking down the site if things get fubar'd? Thanks :)

Khalid Bahey is well on his way to getting a patch into Drupal 6 for spitting out logging of watchdog entries so that:
1. They can be routed to a different source other than the database, from a flat file to syslog support. The watchdog table can crush many sites.
2. Actions can be taken depending on the messages. Get notification via email, IM, pager, etc. depending on the severity levels of messages in your watchdog.

This will be a fantastic feature for Drupal 6....but really, we need it today for Drupal 5 as well. I've spoken with Khalid and he's willing to backport both the patch as well as the supporting modules. The plan of attack is: