Avast_log.ldf is 2GB!

[nsi]

I'm here at server side in which the size of .ldf file is about 3 GB !!!

I have to reduce the ldf size.

a) First of all, when you suggest me to backup the database does it mean backup both database and transaction log ?

b) What does exactly contain the transaction log files. How often does it need to be backed up ?

c) Is it possible to put the ldf files in another path instead of C:\Program Files\Microsoft SQL Server\MSSQL$AVAST\Data
i.e. another disk

d) What happen if a ldf file is deleted ?

Sergio

[Vlk]

Can you give me VPN/remotedesktop access to the machine?
That seems to be the easiest option.

Thanks.

[nsi]

Can you give me VPN/remotedesktop access to the machine?

I'm sorry, we can't access to this server by remote machine.

Could you answer us to the previous post ?


Thanks

Claudio

[Vlk]

a) First of all, when you suggest me to backup the database does it mean backup both database and transaction log ?

Each backup of the log effectively deletes its contents from the database. However, the ldf file is not shrinked because SQL reuses its space.


You can back it up daily, or even multiple times a day. You can delete the backup files of course (they're in <adnm>\data\backup by default). BTW this folder will be real big now if you haven't deleted its contents yet.

b) What does exactly contain the transaction log files. How often does it need to be backed up ?

It's a standard SQL thing. For a detailed explanation, see e.g. http://www.winnetmag.com/SQLServer/Article/ArticleID/9792/9792.html

The ADNM database was set to recovery mode full which makes the log really large. We'll change this to recovery mode simple in the next update to reduce the size of the log (the trade-off is that the recovery possibilities in case of failure will be somewhat limited).

c) Is it possible to put the ldf files in another path instead of C:\Program Files\Microsoft SQL Server\MSSQL$AVAST\Data i.e. another disk

Sorry, this is not possible without the Enterprise manager (or some programming)

d) What happen if a ldf file is deleted ?

If the database is running, the file will be locked so you won't be able to delete it.

[nsi]

I'm at the server side. We could not give you a remote access., but if possible we can make a phone call and try to solve the problem. I need to solve it.

Wait a response

Sergio

[Vlk]

I'd try the following:

1. back up the tx log
2. delete the file with the backup (you won't need it anyway).
3. stop the avast management server service
4. stop the MSSQL$AVAST service
5. delete the .ldf file
6. start the services.

Easy and effective.

[nsi]

Done all 1..6

The MSSQL services has started well

The Avast mng services crash because of

Database check on SBS2003\avast  server failed with 0000A410 error. Use AMS Tool to fix the problem.  

How to use AMS Tool and which module ?

Thanks

Sergio

[Vlk]

And you only deleted the .ldf file?? That's weird -- it shouldn't really care about the log.

Maybe you started it too early -- the MSSQL service might've been restoring the log and therefore denying access to the database.

Please retry it...

You can also use the AMS Tool's "Check DB" command.

Thanks
Vlk

[nsi]

It still doesn't work.
My idea is to wait the very close release of RC_1 and setup the new software.

Have you some timeline of uploading the software ?

Thanks


Sergio