G
gus bjorklund
Guest
> On May 13, 2019, at 12:36 PM, Joey Samoy wrote: > > What would you do after threshold is increased? So transactions completes, no crash, use that value in the db start up param? So if same user scenario happens, you don't get the same warning/error? There is zero correlation between database size and before-image log volume. the rate of before-image log data that is generated is strictly a function of the rate of database changes that are made by the application. the before-image log size is affected by that and by transaction duration (which affects log space reuse). Set the threshold at maybe 6 GB and if you hit that, raise it by 25%. Make sure you have large files enabled and use one variable bi extent and one fixed that are fixed at 4 GB or use a single variable extent.
Continue reading...
Continue reading...