Avast SQL database is 36gig!

Hi all,

I currently have a Avast setup with the database running on an SQL 2005 server cluster. Recently I have noticed the size of the database is growing at an insane rate. It seems to be increasing as I watch it in the windows explorer and is currently sitting at a massive 36gig.

I did a quick query on the database in SQL to see which table was taking up all the space and it showed that the Event table had 131,921,487 rows in it and was taking up 30gig. Don’t know if that helps at all?

Any help appreciated.

How many NetClients do you have?

Do you use the “database tasks” to clean old records?

we have over 3000 clients. I cannot use the database cleanup task as it just hangs and crashes the management service.

dude… 3K clients on one server?? u should spread the clients over 2 or 3 servers

can you not delete the last 750.000 lines with the MS SQL manager itself instead of the cleanup from avast?
how much does the DB grow per day tho?

i am not surprised with that many lines with that many clients tho…
maybe u should run the cleanup wizard (automaticly) more often or lower the days that are kept in the db

Thanks for the input WPN,

Do you have a example query for the SQL cleanup you suggested? SQL is not my Forte :slight_smile:

Thanks again

Some months or year ago I had similar troubles with DB (but in much smaller environment) when DB grow 10 times (350 MB instead of 50 MB) So I restored DB from older backup (after consulting situation with support) and problem disappeared.
Did you use Maintenance tool? Try backup current DB, delete it and create new DB? And watch about growing database as clients will communicate with AMS. When DB will grow quickly, try to set cleaning job (in server tasks) to clean records older then 30 days, or less, instead default value (maybe 90?)

When you delete your current DB you lose your own conditions in dynamic group, which cannot be exported to simple backup file and restored… :frowning: Are you working with your own dynamic groups? If yes, I recommend to make screenshots in wordpad file or other similar “backup” before deleting database…

MS SQL itself isnt my forte either (yet) unfortuanately, so cant help you there

maybe you can file a ticket at support for this, maybe with a link to this topic…

Some time ago; I had a problem like this, but our database file was corrupt causing the services to crash, I uninstalled the ADMN console, deleted the database, installed the ADMN console again, and the clients were reporting to the new console installation again, the only thing we had to do again was to rebuild our computer catalog and move clients, even this event was as a kind of clients update!!

Best Regards!
Sergio