Our Avast Database (full version Microsoft SQL) is 9GB in size. Upon examination, it appears the “Clean Old Records Older Than 1 Month” task has not been running every week, even though it’s scheduled. I’ve tried running this task manually, but it only frees up 100MB or so. It’s not clear if the task actually finishes or is timing out. So, I have a couple questions:
What information is being stored that would take up 9GB of space? Event logs?
Do you have any other suggestions for reducing the current database size? A last resort for us would be to delete it and start over; although I’m not sure what we’d lose.
The space may be taken by reports. Do you generate reports with the “session” as destination? (i.e. to the DB)?
Also, how do you measure the DB size? Just by the size of the underlying files? Or using the SQL Enterprise Manager? Because normally, when you delete data from a database, the space on disk is NOT freed…
We haven’t generated any reports, at least not manually.
We’re measuring the DB size using the SQL Enterprise Manager, although the avast.mdf file also measures 9GB in size. The last steps taken by our server admin were as follows:
Ran “Clean Old Records Older Than 1 Month” task via ADNM Console, let run overnight.
Ran “Shrink Database” command from within SQL Enterprise Manager
I see that this thread just died without a resolution…
however, our DB is now 7GB, gaining about a GB every month. we installed in April 2008 on SQL 2005 (not express) and it’s been growing steadily since.
like the previous user running the ADNM cleanup task doesn’t regain much space and I’m not even going to try to delete and restore because the data will come right back. I am right on the verge of just deleting the DB and creating it new and rebuilding it the hard way but we have 50+ clients and I’m not really looking forward to it. I will if there’s no other solution.
I would really like to know why this is happening. I have other client’s installs on SQL 2005 and this hasn’t been a problem before.
additional info:
when looking at it in SQL Mngmt Studio, all the massive data is in a table called dbo.event, can I just clear this table because it won’t shrink or defragment (only 10% fragmented)? well, it will, but just doesn’t really help.