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 size.
2) If your app does a lot of inserts/updates/deletes, use about 40%-60% of data size.
3) If your app does mostly selects (query intensive), use about 10% of data size.
In applications where I (personally) work with ETL, I disable the transaction log (it's higly not recomended due obvious reasons).
In any case, guarantee that your log backup strategies make Log use not be over 50% of log size. In MaxDB specific, you should activate AutoLog, that will issue a backup log whenever it's necessary. Again, if you define a too small log size, you will have a lot of log backups, decreasing general database performance.
I expect this been helpful.
Edson Richter
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 advance,
Best regards, Andris Spruds
-- MaxDB Discussion Mailing List For list archives: http://lists.mysql.com/maxdb To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
