Page 1 of 1

Performance impact of many timestamped transaction logs

Posted: Tue Sep 29, 2020 2:28 pm
by Adam
Hello all,

In our environment we have a daily SaveDataAll chore running during off-hours. As a consequence, we have accumulated many timestamped tm1s*.log file as we don't presently archive these.

I recall from a prior thread there IS a performance hit with keeping the timestamp'd transaction logs in the log folder when using the Architect transaction log tool. Besides this, any other performance considerations? e.g. with startup? I'm thinking not, but wanted to get the wisdom of the experts.

Thanks!

Re: Performance impact of many timestamped transaction logs

Posted: Tue Sep 29, 2020 9:42 pm
by tomok
Adam wrote:
Tue Sep 29, 2020 2:28 pm
Hello all,

In our environment we have a daily SaveDataAll chore running during off-hours. As a consequence, we have accumulated many timestamped tm1s*.log file as we don't presently archive these.

I recall from a prior thread there IS a performance hit with keeping the timestamp'd transaction logs in the log folder when using the Architect transaction log tool. Besides this, any other performance considerations? e.g. with startup? I'm thinking not, but wanted to get the wisdom of the experts.

Thanks!
The only impact would be on the Architect transaction log searching or if you wanted to back something out. In either case, you would still be crazy not to have a nightly SaveData.