> Of course it depends on your data traffic.
> We have for example a 120 GByte database which mostly has an
> increase of 2-4 GByte/month.
> We have a 1GByte Log volumne which is sufficient enough if
> your are doing daily log backups. I think 50% (60GByte) of
> Log space would be a little bit o
Andris Spruds wrote:
Hello,
How can I tell what's the optimal size for log volume(s)? I know the
question has been asked before, but I could find no satisfactory answers,
also in MaxDB documentation there is information on log volumes in general,
but not about how to choose their size. Thank you in
I think that a very large log size has no other effects than waste of
disk space...
If you need a very really large log volumn, probably you are using wrong
backup strategies.
When anyone need a log > 60% data, is because it's running in ETL (data
import/export). In this case, you can deactiva
Hi,
>>if you define a too small log size, you will have a lot of log backups,
decreasing general database performance.
I have just one question left: what are the consequences if I define too
large log size?
>>I expect this been helpful.
Thank you very much for your asnwer. Indeed, it helped me
Hi, Andris.
There is no cake recipt for log size.
You should evaluate you app log consumption, and define the ideal values.
But, since there is tips every where (any decent SQL database
administration course will tell you):
1) For general purpose transaction related apps, use about 25% of data si
Hello,
How can I tell what's the optimal size for log volume(s)? I know the
question has been asked before, but I could find no satisfactory answers,
also in MaxDB documentation there is information on log volumes in general,
but not about how to choose their size. Thank you in advance,
Best rega
