(This is the same answer I’ve sent via email)
There are advantages and disadvantages of both approaches. I think the
two biggest advantages of log files are the ease of deployment and an
easy way to share log files.
It’s easy to deploy because you do not have to setup another logging
database or database tables, and you do not have to configure any
logging database connections and so on. Depending on how many machines
the deployed application runs on, the deployment issue can be a real
Another advantage is that you can easily copy, share and forward log
files, something that isn’t really practical with data stored in a
database. So if you have a problem on a production server, you can
easily copy or download the log in question (or ask the customer to send
it) and analyze the log file with the Console ‘offline’.
There are of course also advantages of logging to a database. Logging to
a database is easier if you are logging from multiple
processes/machines, as the database synchronizes the different logging
I’m sure there are more advantages and disadvantages of both approaches,
but this really depends on the environment and the purposes of the
We are also looking into adding database support to SmartInspect in the
future, but I cannot say when/if this gets added to the product. If
logging to a database is important, you could also just write a simple
SmartInspect protocol for your environment.