Re: ISA Log to SQL Database Question
- From: "Charlie" <Charlie@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Wed, 17 Aug 2005 18:42:01 -0700
Funny, I just discovered this myself a few hours ago.
I am actually logging to an Access DB and the logs had grown to over 2 GB.
I deleted all the records (after backing them up elsewhere) but it didn't
reduce the size of the DB. I'll look into compacting it.
By the way, I stopped using the DB solution for the logs and went back to
text files, because I was getting errors logging to the DB at least once a
day (probably because of the size). Believe it or not, when ISA wasn't able
to log, it would lose communications with the external NIC. Obviously that
was quite a problem.
"Phillip Windell" wrote:
> Which SQL Database? The MSDE that comes with ISA or the real "full" MS SQL
> Server?
>
> With MSDE the logging interface in ISA lets you set the maximum size limits.
> But if you log to a real SQL Server,..then I believe that has to be
> accomplished independently with the SQL Server itself in some kind of
> scheduled job where it deletes off records that are of a certain age. SQL
> Server isn't my "thing" but you may have to run some kind of compaction
> against the DB after deleting the records to recover drive space because, I
> believe, removing data does not actually make the DB smaller and regain
> drive space on its own.
>
> --
> Phillip Windell [MCP, MVP, CCNA]
> www.wandtv.com
> -----------------------------------------------------
> Understanding the ISA 2004 Access Rule Processing
> http://www.isaserver.org/articles/ISA2004_AccessRules.html
>
> Microsoft Internet Security & Acceleration Server: Guidance
> http://www.microsoft.com/isaserver/techinfo/Guidance/2004.asp
> http://www.microsoft.com/isaserver/techinfo/Guidance/2000.asp
>
> Microsoft Internet Security & Acceleration Server: Partners
> http://www.microsoft.com/isaserver/partners/default.asp
> -----------------------------------------------------
>
>
>
> "Tom Jones" <TomJones@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
> news:ED5BCD9A-AE09-4FA2-B86F-125EC6F29BCB@xxxxxxxxxxxxxxxx
> > Hello all-
> >
> > I have a question about ISA Logging to a SQL Database. We have ISA 2004
> > logging to a SQL 2000 Database and everythign is working fine except for
> the
> > ISA_Log Database that I have created that is logging teh WebProxyLog
> entries
> > is over 3.6GB in size. I only have about 20 of my users going through the
> new
> > ISA server now until we can get some kind of control on the size of thsi
> > database. The tranaction log is ony 1MB and we have the database
> maintenance
> > plan configured to clean up things everday. Is this normal by design if
> you
> > log the WebProxyLog information to a SQL Database that the database will
> grow
> > this big? We are logging almost all of the fields except for 4 in the
> table.
> > I don't know if de-selecting some fields in the table will help.
> >
> > Any Best Practice Advice would be greatly appreciated on loggign the
> > WebProxyLog table to a SQL Database.
> >
> > We are mainly using the SQL Database so we can run our own SQL Queries to
> > generate Web Traffic adn Destination Reports by user etc..
> >
> > Thanks in advance,
> > Tom
>
>
>
.
- Follow-Ups:
- Re: ISA Log to SQL Database Question
- From: Tom Jones
- Re: ISA Log to SQL Database Question
- References:
- ISA Log to SQL Database Question
- From: Tom Jones
- ISA Log to SQL Database Question
- Prev by Date: proxy chain loop
- Next by Date: Re: ISA Log to SQL Database Question
- Previous by thread: Re: ISA Log to SQL Database Question
- Next by thread: Re: ISA Log to SQL Database Question
- Index(es):
Relevant Pages
|
