about every 2 months I have to purchase an additional 100mb of SQL database space. Should not there be a way to trim the database and get rid of old data safely to reduce the db size? Is this a consideration for BV6?


Or should I just shut up and be happy that my store is successful enough to fill up the database space allocated?

I make it a standard practice to do this every month:


1. Review Site Log, address any problems if needed, delete all error messages after reviewed



2. Save Search Terms to excel file for review, delete all search terms



Might help a little bit.

We have many clients with multi GB DB's.

Every cart/order/address/product etc. grows your DB (the .mdb file) regardless of your log size (the .ldf).

I thought you were on a dedi Joe. 100mb increments seems kind of odd on a dedi. Usually it is up to the limit of your storage on the server which should be many GB's.

As Marcus mentioned, make sure the log file isn't running amok. Other than that your user and order history needs to be chopped to see any appreciable reduction.

You may also want to make sure that cart cleanup is REALLY deleting old abandoned carts. Check the BVC_Order table for orders without a value for completedorderid. Sometimes a special character in an order or cart will cause the cleanup process to fail. That can fill up a DB quickly.

In my dev environment I have my database set to SIMPLE recovery model, instead of full. This will greatly reduce the log file size and doesn't hinder the ability of recovery. As long as you have good backups of the db and log files on a regular basis, you will be fine.

Also, a standard sql db maint plan for shrinking and reindexing is always good.

Still, 800MB is small and normal. I'm running at 1GB right now in production, and have another store at 4GB.