Comments
Sort by recent activity
I believe this is the statement that is causing an issue:
SELECT TOP 1 a.type, a.backup_set_uuid, a.first_lsn, a.last_lsn, a.checkpoint_lsn, a.database_backup_lsn, a.media_set_id, c.name
FROM msdb..backupset a INNER JOIN msdb..backupmediafamily b ON a.media_set_id = b.media_set_id INNER JOIN master..sysdatabases c
ON a.database_name COLLATE DATABASE_DEFAULT = c.name COLLATE DATABASE_DEFAULT
WHERE b.physical_device_name = 'SQLBACKUP_D19A5B27-2930-4457-8414-64D9F94BDE6B' ORDER BY a.media_set_id DESC
The device name 'SQLBACKUP_D19A5B27-2930-4457-8414-64D9F94BDE6B' does not exist. In fact it is not even close to what is in that field. This field holds values like
‘[UNC Path]\[backup type]_[sql instance]_[database name]_[date]_[time].sqb’ / comments
I believe this is the statement that is causing an issue:
SELECT TOP 1 a.type, a.backup_set_uuid, a.first_lsn, a.last_lsn, a.checkpoint_lsn, a.database_backup_lsn, a.media_set_id, c.name
FROM msdb....
Ok, I read the log, found the commands that (I thought) were causing the issue. I was able to execute these commands on the database myself without any errors. I do not know how this “division by 0†error is happening. But it still is an issue. / comments
Ok, I read the log, found the commands that (I thought) were causing the issue. I was able to execute these commands on the database myself without any errors. I do not know how this “division ...
I am getting the same error/Warning (Warning 166), but running the task manually does not fix it. Is there a way that I can view this log data and remove whatever it is that is causing this issue? / comments
I am getting the same error/Warning (Warning 166), but running the task manually does not fix it. Is there a way that I can view this log data and remove whatever it is that is causing this issue?