Ben

I've noticed this in one environment across different SQL Versions where this issue occurs. It happens infrequently enough where I just re-run the Full backup to resolve, but my error...

If I see the error occur in the environment I've noticed it in previously, I'll try to dig into it and see what I can find and report back here....

Can you send a portion of the MSDB history for one of the databases experiencing the issue? Something like the results from: SELECT TOP(50) * FROM msdb..backupset WHERE database_name =...

I had troubleshooted via email with Clifton and was able to determine that his differential backups were failing because there was a full non-copy-only snapshot backup taking place before his...

You need to specify the database name that's having the issue in the database_name = '' And just let me know the best email to reach you at and I'll...

I believe Clifton's issue was with Azure Backups, as it's taking a Full snapshot backup of the database, but the backup isn't copy-only so it breaks the differential chain as...

Why not just script out renaming the job and have it run after you deploy the OLA Jobs? Something like: `USE [msdb] GO EXEC msdb.dbo.sp_update_job @job_name=N'CommandLog Cleanup', @new_name=N'_MAINT_CommandLog Cleanup',@enabled=1 GO`...

I use this across various environments with varying SQL Versions, and have not had this occur before and have used every single parameter you've used EXCEPT for @DatabaseOrder = 'DATABASE_SIZE_DESC'...

Why not just script out renaming the job and have it run after you deploy the OLA Jobs? Something like: `USE [msdb] GO EXEC msdb.dbo.sp_update_job @job_name=N'CommandLog Cleanup', @new_name=N'_MAINT_CommandLog Cleanup',@enabled=1 GO...

Hey wfvdijk I know it's not entirely what you're asking for, but why not have the two log backup jobs run in parallel but exclude that extremely large database and...