http://www.aspfaq.com/2473




[quoted text, click to view]

Are there any free components out there that will analyse IIS log files and
write selected information to a DB?

I know there are free packages like Analog and Webalizer, but I'm more
interesting in an app or component that feeds log files in to a DB so that
it can be queried later.

Thanks

[quoted text, click to view]

Analog will create a machine-readable file that can easily be imported
into a database, or you can use Microsoft's Log Parser tool with a
little work. You could also simply log to an ODBC database from IIS
for real-time access.

At any rate, a log file is simply a text file, easily imported into
almost any database without a component.

[quoted text, click to view]

or your favourite spreadsheet if that's more convenient.

--
William Tasso - http://WilliamTasso.com

[quoted text, click to view]

Granted, not everyone can afford to license Windows Server 2003 on their
day-to-day desktop. Even with a proper MSDN license, there's a fine line
between "development and testing" and "business use."

A

I've actually followed one of Aarons links, and now I'm logging directly to
SQL Server. Marvellous!

One thing that did puzzle me for a short while was that the ODBC option does
not appear to be available in XP/IIS5.1. This is not a problem for me except
that I cant try things out on my development machine.

Thanks


[quoted text, click to view]

[quoted text, click to view]

XP is not a server - you really should consider building a dev environment
that mimicks the functionality of your production set up.

--
William Tasso - http://WilliamTasso.com

Thats a fair point Aaron, but I guess I am 'lucky' in that I do in fact have
a W2K server for development. Ok, it's a bit old, but it does the job.

But in answer to Williams point:

There is a hierarchy of machines used in the process. I develop the basic
code on my XP machine. It is uploaded and tested on the development server.
Anomalies are fixed. After enough testing, it is released to one production
server. After user testing, it is rolled out to remaining production
servers. If I were to use the development server for all my development
work, I would cause a lot of inconvenience/problems for the other developers
who share the server, hence XP is used in the first instance.

After a bit of head scratching I did finally find the answer on our
development server...

But my point still stands. I'm surprised it doesnt appear in IIS5.1. This
*is* a genuine web server and there is no reason why this ODBC feature
couldnt have been included.

I'm sure His Royal Billness had his reasons for this, but it's academic -
things are the way they are. Its only a minor inconvenience anyway.

Cheers

Chris

[quoted text, click to view]