Large Database Size

[Former Member]

Hi!

One of our clients has been running B1 for about two years now with a monthly load of 2000-3000 document cycles (that would be 3000 of each SO, DN, IN and IncPmts).

The database is now a healthy 18GB file.

The files are distributed as 200MB on each document header table (OINV, ORDR, etc) and 2GB on each line level table (INV1, RDR1 etc). The ADOC is about 1GB and the ADO1 is about 5GB.

I imagine the DB will only keep growing, possibly slowing down operations and reporting in a couple of years from now, not to mention of copying the DB to support if anything breaks...

Do you know of any recommendations for database maintenance?

Have you seen any documentation on this topic on the partner portal?

Thank you!

Liviu

[former_member186095 · Accepted solution]

Hello,

you could find it in this threat:

you could find recomendation and SBO database size estimator.

Rgds,

[Former Member · Accepted solution]

Thanks, Jimmy!

I saw that thread earlier, nice tools and advice, however, even using those estimates (which are half of what the actual is), in 5 years the database would grow to 30GB. I can tell that it will grow to 60GB!

Imagine that you have to take daily backups etc. Running any reports can take a very long time, only parsing through all that amount of data.

Did you see anything on the forums for what to do when the database file grows past a comfortable size?

I imagine you would create a new company and import beginning balances, but I was wondering if there is any 'recommended' cleaner way of 'archiving' posting years as you go (let's say, 'archive' 2004 fiscal year to an external database that would not be used except for history, or some off reporting).

Thanks for the quick reply!

Liviu

[former_member186095 · Accepted solution]

Hello,

I see that it will be like that. The database growth is not stopped but increasing.

One of the solution is to create a new database and import beginning balance (as you have said).

If archiving is preferred, you must use addon for that and it is available in this link:

https://websmp208.sap-ag.de/~sapidb/011000358700004044122006E/

The database log file can be shrink and it is really useful although will not give a 80% impact.

Rgds,

[Former Member · Accepted solution]

True, the log file can get large, however, if you use Simple and auto shrink for the database settings, this file stays quite small without you having to shrink it manually.

I looked over the list of addons, did you have one in mind in particular?

Thanks!

Liviu

[former_member186095 · Accepted solution]

I do not have time to checked or find out what inside the addon. I am a certified implementation solution of one of the addon (Job costing). it is good addon and best practice. So, if SAP approved it, I think the other is the best too.

The old and closed transactions seems very important for you. Although, it is not giving any benefit except if you have repeat sales, repeat transaction, repeat payment, etc in the same amounts and quantities and in the same customers.

So, I suggest to use copy express addon for faster new database creation. And just close the 15 GB database if it has made the server slow in its performance.

Rgds

[Former Member · Accepted solution]

Good advice. Thank you!

Liviu