RE: test
- From: "cismic" <cismic@xxxxxxx>
- To: "'[ISAserver.org Discussion List]'" <isalist@xxxxxxxxxxxxx>
- Date: Wed, 26 Sep 2001 16:45:21 -0700
Darren,
I've actually decided to not use SQL Logging for ISA Machines or IIS
machines. I have used it in the past and it works well. However, I
think that the hits against ISA, and SQL during virus attempts is far
too much band width for me to give up.
It has been easier and more efficient to parse the information daily.
I'm still using the same structure of the database that the SDK scripts
use. This has made it easier to create joins and such from sources that
I need reporting on. I just don't want the constant hit against my any
of my SQL machines.
I appreciate your input very much!
Joseph
-----Original Message-----
From: Darren [mailto:darren.lacy@xxxxxxxxxxxxxxxxxx]
Sent: Wednesday, September 26, 2001 6:39 AM
To: [ISAserver.org Discussion List]
Subject: [isalist] RE: test
http://www.ISAserver.org
Joseph:
I had exactly the same needs as you for analyzing ISA logs. Here was my
approach.
Configure ISA to log directly to SQL Server through an ODBC connection,
(This works with IIS as well). Be careful to set it up correctly since
the ISA services will not start if they can't write to their log. The
install CD even contains the SQL scripts necessary to automatically
generate the tables and default indexes ISA needs. You can run these in
Enterprise Manager or Query Analyzer. Then you can use what ever
reporting tools you have at your disposal to pull the data from the
database.
If you need, or would like any other details about logging directly to
SQL
Server, feel free to send me a note at darren.lacy@xxxxxxxxxxxxxxxxxxx
Hope this helps,
Darren Lacy
Decision Source, Inc.
------------------------------------------------------
You are currently subscribed to this ISAserver.org Discussion List as:
cismic@xxxxxxx
To unsubscribe send a blank email to $subst('Email.Unsub')
Other related posts:
