ADNM Growing Database

[system]

Hi guys,

Clean Records Older Than 3 Month doesn’t work and Database is growing everyday. We manually deleted the entries in Database and we have now like 24 GB free space!

Avast saves all successfull events, logons, scans. Is there a way to stop ADNM logging successfull events/logs to the SQL Database?

Thanks in advance,

luna

[system]

Simple way - restore DB from backup
Otherwise you can try install Management studio and run CHECKDB utility and other, when your are familiar with MS SQL…

[system]

So is there no way to stop some Events like success update of clients / scan logs from logging to the sql database?

[system]

@e2e2 post:3

So is there no way to stop some Events like success update of clients / scan logs from logging to the sql database?

I’m not sure, if it is necessary… I had never such requirement. What about more information about your environment (how many clients…)???
I suppose, there must be problem with database, not in number of logged events. Database size in environment 3 Netservers and 60 Netclients is about 50-60 MB, not more. 24 GB is over my fantasy
Two years ago I recognized grow of my DB backups up to 300+ MB, but restore DB helped me.

[system]

Yesterday dbo.ShortName and dbo.Results had 0 records. Now it is over 2 million.

Avast logs every scanned file from clients and servers to the dbo.Shortname table.

We have 7 servers and like 50 clients.

There must be a setting to disable this in ADNM 4.8.

[InfratechSolutions]

What version of MS SQL are you using: MSDE, 2003, 2008?

[system]

@e2e2 post:5

Avast logs every scanned file from clients and servers to the dbo.Shortname table.
…There must be a setting to disable this in ADNM 4.8.

Yes, what about logging level settings?
See Properties of appropriate computer group in your computer catalog. I use Alert level, second option in right column. See enclosed image (ADNM console is in Czech version)

[system]

@edj post:6

What version of MS SQL are you using: MSDE, 2003, 2008?

We are using SQL 2008 64bit

@Paba post:7

@e2e2 post:5

Avast logs every scanned file from clients and servers to the dbo.Shortname table.
…There must be a setting to disable this in ADNM 4.8.

Yes, what about logging level settings?
See Properties of appropriate computer group in your computer catalog. I use Alert level, second option in right column. See enclosed image (ADNM console is in Czech version)

We have the same settings.

[InfratechSolutions]

In MS SQL a database has two files:

• avast.mdf

• avast_log.ldf

Which file is 24 GB? I suppose that is the avast_log.ldf, isn’t it?

[system]

@edj post:9

In MS SQL a database has two files:

• avast.mdf

• avast_log.ldf

Which file is 24 GB? I suppose that is the avast_log.ldf, isn’t it?

Yes it’s the avast_log.ldf.

dbo.ShortName and dbo.Results table entries are now over 3 million. We deleted the entries manually 2 day ago

[system]

You are using paid version SQL server, not Express? Than you can set maintenance plan and shrink log file as SQL job.

@e2e2 post:10

dbo.ShortName and dbo.Results table entries are now over 3 million. We deleted the entries manually 2 day ago

I never manually delete rows in that tables, and I have ~ 60 000 rows. I only use standard server task (delete events older 3 months)

[InfratechSolutions]

We had the same problem in one of our customers with 4000 machines.

The problem is not ADNM, is MS SQL and thr transaction log file.

You can change the SQL Database properties to SIMPLE:

http://msdn.microsoft.com/en-us/library/ms189275.aspx

[system]

@Paba post:11

You are using paid version SQL server, not Express? Than you can set maintenance plan and shrink log file as SQL job.

@e2e2 post:10

dbo.ShortName and dbo.Results table entries are now over 3 million. We deleted the entries manually 2 day ago

I never manually delete rows in that tables, and I have ~ 60 000 rows. I only use standard server task (delete events older 3 months)

It is paid SQL server.

[system]

@edj post:12

We had the same problem in one of our customers with 4000 machines.

The problem is not ADNM, is MS SQL and thr transaction log file.

You can change the SQL Database properties to SIMPLE:

http://msdn.microsoft.com/en-us/library/ms189275.aspx

It is already SIMPLE.

See the queries

[system]

And the ShortNames Table

[system]

@e2e2 post:13

It is paid SQL server.

And are you familiar with SQL server administration? Are you able to set shrinking job? Otherwise I can find T-SQL command on my servers and post it here…

[system]

@edj post:12

We had the same problem in one of our customers with 4000 machines.

The problem is not ADNM, is MS SQL and thr transaction log file.

You can change the SQL Database properties to SIMPLE:

http://msdn.microsoft.com/en-us/library/ms189275.aspx

@Paba post:16

@e2e2 post:13

It is paid SQL server.

And are you familiar with SQL server administration? Are you able to set shrinking job? Otherwise I can find T-SQL command on my servers and post it here…

I just changed the database clean up to 1 day to try out and database is now 20 MB.

I will make it 1 week so after a week it will clean the database.

Thanks for your help.

[system]

When the main problem with growing database is in logfile, try to set following job in SQL server Agent:
1.step: backup LOG Avast WITH NO_LOG
2.step: use [Avast]DBCC SHRINKFILE (N’Avast_log’, 15)

When database is partially harmed, the best way is delete + create new DB in Maintenance tool, or recreate from older backup. Disadvantage - You will lose your special settings and dynamic conditions, (if you use any…)