I am in the process of adding the
WITH CHECKSUM flag on our daily SQL backups, as part of an effort to better ensure data integrity.
I definitely want to know if a checksum error is ever encountered, but I also don't want my job to stop dead in the water in the middle of the night; I want it to finish backing up the "bad" database, then continue backing up the other databases on the server.
If I use
BACKUP WITH CHECKSUM, CONTINUE_AFTER_ERROR, will it still throw the appropriate error (
SEV 22 or
Error 825 or whatever) that will trigger my associated alert? Or does
CONTINUE_AFTER_ERROR suppress this altogether, and I'd only know about the problem if I parse the job step output?
I would simply test it, but I don't have a database with known