<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Backup on SQLNikon</title><link>https://sqlnikon.com/tag/backup/</link><description>Recent content in Backup on SQLNikon</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Tue, 11 Feb 2014 12:40:12 +0000</lastBuildDate><atom:link href="https://sqlnikon.com/tag/backup/index.xml" rel="self" type="application/rss+xml"/><item><title>T-SQL Tuesday #51 - Don't bet against CHECKSUM when performing backups</title><link>https://sqlnikon.com/2014/02/11/t-sql-tuesday-51-dont-bet-against-checksum-when-performing-backups/</link><pubDate>Tue, 11 Feb 2014 12:40:12 +0000</pubDate><guid>https://sqlnikon.com/2014/02/11/t-sql-tuesday-51-dont-bet-against-checksum-when-performing-backups/</guid><description>&lt;p&gt;&lt;a href="http://jasonbrimhall.info/2014/02/04/t-sql-tuesday-051-place-your-bets/"&gt;&lt;img src="https://sqlnikon.com/wp-content/uploads/2014/01/t-sql-tuesday.png" class="size-full wp-image-630 alignnone" width="150" height="150" alt="Automating repetitive tasks" /&gt;&lt;/a&gt;This month&amp;rsquo;s T-SQL Tuesday is being hosted by Jason Brimhall (&lt;a href="http://jasonbrimhall.info/"&gt;blog&lt;/a&gt; | &lt;a href="https://twitter.com/sqlrnnr"&gt;Twitter&lt;/a&gt;).  Jason&amp;rsquo;s theme is about gambling with SQL Server.  What areas have you gambled with?  Are there tasks that you should be doing that you are betting won&amp;rsquo;t be needed?  One came to mind for me, CHECKSUM.  I&amp;rsquo;ve always been a fan of Maintenance Plans.  They are an easy way to get basic maintenance tasks established on an instance of SQL Server.  The major down side of the built-in maintenance plans is no support for the CHECKSUM media option for &lt;a href="http://technet.microsoft.com/en-us/library/ms186865.aspx"&gt;BACKUP DATABASE&lt;/a&gt;.  If you are performing backups without this option enabled, you run the risk of the pages in the backup media not matching the pages stored in the database.  This is because without the CHECKSUM option, SQL Server doesn&amp;rsquo;t know if the page written to the backup media was written out correctly.  The CHECKSUM option ensures that every page written out to your backup media has a checksum that matches the checksum of the page in the database.  The CHECKSUM option also goes as far as doing a checksum on the entire backup that the &lt;a href="http://technet.microsoft.com/en-us/library/ms186858.aspx"&gt;RESTORE&lt;/a&gt; statement can take advantage of.  There is a performance impact for using the CHECKSUM option but as everyone says, your backup is only as good as your restore.  If you bet against your restore, your odds of a resume updating event just increased.&lt;/p&gt;</description></item></channel></rss>