• The one question is did they restore the "BACKUP Log With TRUNCATE_ONLY" option?

    I have been in so many situations that I walk in after a bulk data load or a replication failure and the system is down because the tran log is full and there is no space on disk. There is no way to get the system up while you troubleshoot the problem.

    I have had to try to add an additional log file with no disk space on the original file to accept the command because the first tran file is full.

    Then the argument is why are you in full recovery? Because I need a general Piont-In-Time recovery option. The fact that the SQL Server agent failed is not the cause that the backups didn't get done. It is the incompetent DBA that didn't choose the right backup model.



    ----------------
    Jim P.

    A little bit of this and a little byte of that can cause bloatware.