Eitan Blumin shares some recommendations:
In many SQL Server environments, DBAs configure SQL Agent jobs with retry attempts (which is a smart move to handle transient issues gracefully). But with it comes a hidden pitfall that often goes unnoticed:
Retry-enabled job steps can silently overwrite logs or cause runaway log growth, depending on how the output file is configured.
The culprit? Improper use of append settings and missing time-based tokens in output file paths.
Read on to learn more.