Log Analyzer 5.35 and SQL database

[mcclelland2007]

We currently have Log Analyzer 5.35 set up to log to a SQL 2000 database and are experiencing some EXTREME slowness when opening the log file. The database is up and running, Host Monitor is working perfectly, but it takes about an hour to open up Log Anayzer.

Is there any light at all that anyone can shed on this?

[KS-Soft]

How big is log table?

Regards
Alex

[mcclelland2007]

Alex,

The log table is 16297732 rows. Is that what you were looking for?

[KS-Soft]

LogAnalyzer processes data with average speed 4-20 thousand records per second (depends on table settings, hardware, etc). 16297732/4000/60=67 minutes.
I would recommend to use one of standard date filters:
- analyze current week only
- analyze current month only
Also you may use some custom filters
http://www.ks-soft.net/hostmon.eng/la/i ... dbcManager

Regards
Alex

[mos-eisley]

I have created some Views in the database to select from, instead of the complete table, the view have a whereclause that limits the number of records returned, You can use like getdate()-7 to only see the last 7 days.

[KS-Soft Europe]

I have created some Views in the database to select from, instead of the complete table, the view have a whereclause that limits the number of records returned, You can use like getdate()-7 to only see the last 7 days.

Yep, creating Views is a good solution. However, you may achieve the same goal using Log Analyzer itself. As you know, when you setup an ODBC Log, you may specify additional filter that will be used in "Where" part of the SQL statement using "Add custom filter option". Quote from the manual:
http://www.ks-soft.net/hostmon.eng/la/i ... dbcManager
============================
Add custom filter
Here you may provide additional filter that will be used in "where" part of the SQL statement. For example you may use this filter to select information about some specific test item (testname='main router')
============================

Regards,
Max