Sage 300

Sage 300 2014, keeping 10 years of history. 7/15/15 SQL database was 104GB. 13 months later it is 330GB. Sample from a large table: APIBD was 6,272,688 rows at 11,577MB, now 7,572,928 rows but 29,633MB. Any ideas on why the DB size growth not proportional to number of records? Anything to be done about it?

@PhilMcIntosh - did you do a recent upgrade? What is the database recovery model set at? It should be simple.

It's not the log file that is out of control - that gets shrunk regularly as part of the maintenance plan. The upgrade to 2014 was done well before the copy I have from July 2015

We have seen where setting the recovery will change the database size. Also have you re

Reindexed the database or performed a dump/load

re-indexing was recently added to the weekly database maintenance plan

I have gotten all the technical people to agree to the dump/load. Now to get management to agree on a time to actually do it...

@PhilMcIntosh - Check out the TaiRox utility for Fast DBLOAD. It will save a lot of time for large database loads.

Yes I have quoted them that. They already have a couple of other Tairox programs. Thank you for your help on this!

So they bought the Tairox utility. We ran it this weekend along with purging AR & AP and at the end of the load the database was 102GB. Then I logged in Sunday morning to run scripts to put back the custom objects and noticed that the database was growing right before my eyes with no one in the system. It finally stopped at about 206 GB. Just now, I got an email back from the corporate IT person who first asked why the database had gotten so large: ""There is a job scheduled every Sunday at 3:00 AM. It rebuilds the indexes on the Accpac database. It changes free space per page to 80%."" Well now we know why the database size ballooned...but not why they were asking me about it...

@PhilMcIntosh - You have to love internal IT departments! Nothing is their fault and it's always the software or the implementer. They shouldn't have to rebuild the indexes on an Accpac database weekly. Maybe every 6 months, but doing the DUMP/LOAD is a better process for Sage 300 (ACCPAC).