<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Backup Audit on SQL Server Scripts</title><link>https://www.sqlserver70.com/tags/backup-audit/</link><description>Recent content in Backup Audit on SQL Server Scripts</description><generator>Hugo -- gohugo.io</generator><language>en</language><copyright>SQLServer70.com</copyright><lastBuildDate>Sun, 19 Apr 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://www.sqlserver70.com/tags/backup-audit/index.xml" rel="self" type="application/rss+xml"/><item><title>SQL Server: Find Databases With No Recent Backup</title><link>https://www.sqlserver70.com/post/sql-server-find-databases-no-recent-backup/</link><pubDate>Sun, 19 Apr 2026 00:00:00 +0000</pubDate><guid>https://www.sqlserver70.com/post/sql-server-find-databases-no-recent-backup/</guid><description>
&lt;p&gt;Finding databases that have not been backed up recently is one of the most important checks a DBA can run. A database that grows unnoticed without a backup is a data loss event waiting to happen. This script queries &lt;code&gt;msdb.dbo.backupset&lt;/code&gt; against &lt;code&gt;sys.databases&lt;/code&gt; to surface any online user database with no full backup in the last 24 hours, or that has never been backed up at all.&lt;/p&gt;
&lt;script async src="https://pagead2.googlesyndication.com/pagead/js/adsbygoogle.js?client=ca-pub-1012089347386563"
crossorigin="anonymous"&gt;&lt;/script&gt;
&lt;ins class="adsbygoogle"
style="display:inline-block;width:728px;height:90px"
data-ad-client="ca-pub-1012089347386563"
data-ad-slot="8593449130"&gt;&lt;/ins&gt;
&lt;script&gt;
(adsbygoogle = window.adsbygoogle || []).push({});
&lt;/script&gt;
&lt;h2 id="purpose-and-overview"&gt;Purpose and Overview&lt;/h2&gt;
&lt;p&gt;SQL Server does not alert you by default when a database backup is overdue. If a scheduled backup job fails silently or a new database is created without being added to the backup plan, that database will accumulate changes with no recovery point. The only way to detect this proactively is to query the backup history in &lt;code&gt;msdb&lt;/code&gt;.&lt;/p&gt;</description></item></channel></rss>