<?xml version="1.0" encoding="UTF-8" standalone="no"?><rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:sy="http://purl.org/rss/1.0/modules/syndication/" xmlns:wfw="http://wellformedweb.org/CommentAPI/" version="2.0">

<channel>
	<title>MarlonRibunal.com</title>
	<atom:link href="https://marlonribunal.com/feed/?max-results=10" rel="self" type="application/rss+xml"/>
	<link>https://marlonribunal.com</link>
	<description>SQL, Code, Coffee, etc.</description>
	<lastBuildDate>Tue, 03 Nov 2026 22:32:55 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	<generator>https://wordpress.org/?v=7.1.4</generator>
	<xhtml:meta content="noindex" name="robots" xmlns:xhtml="http://www.w3.org/1999/xhtml"/><item>
		<title>Are Blogs Still Relevant? I Think They Still Are.</title>
		<link>https://marlonribunal.com/are-blogs-still-relevant-i-think-they-still-are/</link>
					<comments>https://marlonribunal.com/are-blogs-still-relevant-i-think-they-still-are/#respond</comments>
		
		<dc:creator><![CDATA[Marlon Ribunal]]></dc:creator>
		<pubDate>Tue, 10 Nov 2026 14:15:00 +0000</pubDate>
				<category><![CDATA[Career]]></category>
		<category><![CDATA[Learning]]></category>
		<category><![CDATA[SQL Server]]></category>
		<guid isPermaLink="false">https://marlonribunal.com/?p=3158</guid>

					<description><![CDATA[<p>As for me, I'll keep writing whenever time permits. I don't expect every post to get hundreds of views or generate a lot of discussion. If someone finds an article useful, learns something new, or approaches a problem differently because of something I wrote, that's already a good reason to keep doing it. <a href="https://marlonribunal.com/are-blogs-still-relevant-i-think-they-still-are/">Continue reading <span class="meta-nav">&#8594;</span></a></p>
<p>The post <a href="https://marlonribunal.com/are-blogs-still-relevant-i-think-they-still-are/">Are Blogs Still Relevant? I Think They Still Are.</a> first appeared on <a href="https://marlonribunal.com">SQL, Code, Coffee, Etc.</a>.</p>]]></description>
										<content:encoded><![CDATA[<p class="wp-block-paragraph">This post is my contribution to <a href="https://desertdba.com/t-sql-tuesday-204-are-blogs-still-relevant/">T-SQL Tuesday #204 – Are Blogs Still Relevant?</a>, hosted by Jeff Iannucci (<a href="https://desertdba.com/" target="_blank" rel="noopener nofollow">b</a> | <a href="https://www.linkedin.com/in/jeff-iannucci/" target="_blank" rel="noopener nofollow">li </a>). Please check Jeff&#8217;s invitation post for the rules. </p>


<div class="wp-block-image">
<figure class="alignright size-full is-resized"><a href="https://desertdba.com/t-sql-tuesday-204-are-blogs-still-relevant/"><img fetchpriority="high" decoding="async" width="420" height="420" src="https://marlonribunal.com/wp-content/uploads/2026/08/TSQL_Tuesday_Logo.png" alt="T-SQL Tuesday" class="wp-image-2872" style="width:193px;height:auto" srcset="https://marlonribunal.com/wp-content/uploads/2026/08/TSQL_Tuesday_Logo.png 420w, https://marlonribunal.com/wp-content/uploads/2026/08/TSQL_Tuesday_Logo-300x300.png 300w, https://marlonribunal.com/wp-content/uploads/2026/08/TSQL_Tuesday_Logo-150x150.png 150w" sizes="(max-width: 420px) 100vw, 420px" /></a></figure>
</div>


<p class="wp-block-paragraph"><a href="https://tsqltuesday.com/" target="_blank" rel="noopener nofollow">T-SQL Tuesday</a> is a monthly blogging event in the SQL Server community, started by Adam Machanic in 2009 and now maintained by Steve Jones. Each month, a different community member hosts the event by proposing a topic, inviting SQL Server professionals and enthusiasts to share their experiences, knowledge, and thoughts through blog posts.</p>



<p class="wp-block-paragraph">It&#8217;s a great way to learn from others, discover new voices in the community, and keep the spirit of knowledge sharing alive.</p>



<p class="wp-block-paragraph">This month&#8217;s topic is: Are blogs still relevant?</p>



<p class="wp-block-paragraph">It&#8217;s hard to tell whether people in the technology community still read blogs as much as they used to. With AI tools becoming more accessible, someone can simply ask ChatGPT, Claude, or another AI assistant a question and get an answer in seconds.</p>



<p class="wp-block-paragraph">Why spend time searching through blog posts when you can just ask AI?</p>



<p class="wp-block-paragraph">If we&#8217;re talking about popularity, I don&#8217;t think blogs have the same presence they had back in the 2010s. There are so many other ways to consume information now. YouTube, podcasts, social media, newsletters, and AI assistants have all changed how we learn and discover things.</p>



<p class="wp-block-paragraph">But if the question is whether blogs are still relevant, I would say yes.</p>



<h2 class="wp-block-heading">There&#8217;s Still Value in Reading Someone Else&#8217;s Experience</h2>



<p class="wp-block-paragraph">One thing I appreciate about technical blogs is that they often come from someone who actually encountered a problem, spent time figuring it out, and decided to share what they learned.</p>



<p class="wp-block-paragraph">Take SQL Server, for example.</p>



<p class="wp-block-paragraph">You can ask AI how to troubleshoot a slow-running query, how to interpret wait statistics, or how to configure a particular SQL Server feature. It will probably give you a reasonable starting point.</p>



<p class="wp-block-paragraph">But there&#8217;s a difference between getting an answer and understanding how someone arrived at that answer.</p>



<p class="wp-block-paragraph">A blog post can explain what the author tried, what worked, what didn&#8217;t, and why a particular approach made sense in their environment. Sometimes, the most useful part isn&#8217;t even the final solution. It&#8217;s the troubleshooting process that got them there.</p>



<p class="wp-block-paragraph">And that&#8217;s something I still enjoy reading.</p>



<p class="wp-block-paragraph">I&#8217;ve come across plenty of situations where I thought I understood a particular SQL Server behavior, only to discover something different when I started testing it myself. Reading about someone else&#8217;s experience can give you a different perspective and sometimes save you hours of investigation.</p>



<p class="wp-block-paragraph">Of course, not every blog post is accurate, and not every solution applies to every environment. That&#8217;s part of being a technology professional. We still need to validate what we read and understand how it applies to our own circumstances.</p>



<h2 class="wp-block-heading">AI Has Changed How We Write</h2>



<p class="wp-block-paragraph">Here&#8217;s another thing I&#8217;ve been thinking about.</p>



<p class="wp-block-paragraph">I keep writing blog posts whenever time permits. And honestly, there are fewer excuses now for not putting something out there.</p>



<p class="wp-block-paragraph">One of the hurdles for many people who want to blog is writing itself. They might know the technology, understand a particular problem, and have something valuable to share, but putting those thoughts into a well-written article can be difficult.</p>



<p class="wp-block-paragraph">Grammar, sentence construction, organization, and simply finding the right words can get in the way.</p>



<p class="wp-block-paragraph">I&#8217;ve been there myself.</p>



<p class="wp-block-paragraph">Now we have AI tools that can help organize our thoughts, improve sentence construction, check grammar, and make an article easier to read.</p>



<p class="wp-block-paragraph">That doesn&#8217;t mean we should let AI do all the thinking for us. We still need to bring our own experience, technical knowledge, research, and judgment to the table.</p>



<p class="wp-block-paragraph">I&#8217;ve started using AI in my own writing and technical experiments.</p>



<p class="wp-block-paragraph">For example, in my recent post about <a href="https://marlonribunal.com/when-do-you-reach-for-a-temp-table/">When Do You Reach For A #temp Table?</a>, I used Claude Code to help generate test scenarios. That saved me time setting up the experiments so I could concentrate on examining the behavior and explaining what I found.</p>



<p class="wp-block-paragraph">AI helped with the process, but I still needed to understand the SQL Server behavior, review the results, and decide what was worth sharing.</p>



<p class="wp-block-paragraph">I think that&#8217;s a pretty good way to use these tools.</p>



<p class="wp-block-paragraph">If you know something worth sharing but struggle to put it into words, there&#8217;s no reason to let grammar or writing skills stop you. Let AI help you communicate what you know.</p>



<h2 class="wp-block-heading">We Should Be Seeing More Quality Technical Content</h2>



<p class="wp-block-paragraph">If AI makes writing easier, shouldn&#8217;t we be seeing more blog posts from the technology community?</p>



<p class="wp-block-paragraph">I think so.</p>



<p class="wp-block-paragraph">There are plenty of SQL Server professionals out there with years of experience. They have dealt with production outages, performance problems, migrations, database corruption, security issues, and all sorts of situations that don&#8217;t always have a straightforward answer.</p>



<p class="wp-block-paragraph">Those experiences are worth sharing.</p>



<p class="wp-block-paragraph">Imagine how much more we could learn if more people took the time to document what they encountered and what they learned along the way.</p>



<p class="wp-block-paragraph">We don&#8217;t all have to write comprehensive technical guides. Sometimes a short post explaining a particular problem, a useful script, a troubleshooting tip, or a lesson learned from a production incident is already valuable.</p>



<p class="wp-block-paragraph">And you don&#8217;t have to be a well-known name in the community to have something worth sharing.</p>



<p class="wp-block-paragraph">Someone might be troubleshooting the exact same problem months or even years from now. Your post could be the one that helps them move forward.</p>



<p class="wp-block-paragraph">That&#8217;s one of the things I like about blogging. A post can continue to be useful long after you publish it.</p>



<h2 class="wp-block-heading">So, Are Blogs Still Relevant?</h2>



<p class="wp-block-paragraph">For me, absolutely.</p>



<p class="wp-block-paragraph">Are blogs as popular as they were in the 2010s? Probably not. Do I expect people to spend hours browsing through technical blogs when they can ask an AI assistant for an answer? Probably not either.</p>



<p class="wp-block-paragraph">But I don&#8217;t think those things make blogging any less valuable.</p>



<p class="wp-block-paragraph">AI is another tool we can use to learn, research, and communicate. It can make finding information and putting our thoughts into words easier. But there&#8217;s still value in reading about the experiences and discoveries of people who work with the technology every day.</p>



<p class="wp-block-paragraph">As for me, I&#8217;ll keep writing whenever time permits. I don&#8217;t expect every post to get hundreds of views or generate a lot of discussion. If someone finds an article useful, learns something new, or approaches a problem differently because of something I wrote, that&#8217;s already a good reason to keep doing it.</p>



<p class="wp-block-paragraph">And if AI can help me spend less time worrying about grammar and more time sharing what I&#8217;ve learned, I&#8217;ll gladly take that help.</p>



<p class="wp-block-paragraph">Now, I&#8217;d like to hear from the rest of the community.</p>



<p class="wp-block-paragraph">Are you still reading technical blogs? Have you changed how you learn because of AI? And if you&#8217;ve stopped blogging, what&#8217;s holding you back?</p>



<p class="wp-block-paragraph">Let&#8217;s keep sharing what we learn.</p>



<p class="wp-block-paragraph">Happy T-SQL Tuesday!</p><p>The post <a href="https://marlonribunal.com/are-blogs-still-relevant-i-think-they-still-are/">Are Blogs Still Relevant? I Think They Still Are.</a> first appeared on <a href="https://marlonribunal.com">SQL, Code, Coffee, Etc.</a>.</p>]]></content:encoded>
					
					<wfw:commentRss>https://marlonribunal.com/are-blogs-still-relevant-i-think-they-still-are/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
		<item>
		<title>The Proof of the Backup Is in the Pudding</title>
		<link>https://marlonribunal.com/the-proof-of-the-backup-is-in-the-pudding/</link>
					<comments>https://marlonribunal.com/the-proof-of-the-backup-is-in-the-pudding/#respond</comments>
		
		<dc:creator><![CDATA[Marlon Ribunal]]></dc:creator>
		<pubDate>Tue, 03 Nov 2026 14:15:00 +0000</pubDate>
				<category><![CDATA[SQL Server]]></category>
		<category><![CDATA[Tools]]></category>
		<guid isPermaLink="false">https://marlonribunal.com/?p=3154</guid>

					<description><![CDATA[<p>For me, the objective is straightforward: have a backup strategy that is reliable, understandable, maintainable, and, most importantly, restorable. A successful backup job is good news. A successful restore is proof that your backup strategy actually works. <a href="https://marlonribunal.com/the-proof-of-the-backup-is-in-the-pudding/">Continue reading <span class="meta-nav">&#8594;</span></a></p>
<p>The post <a href="https://marlonribunal.com/the-proof-of-the-backup-is-in-the-pudding/">The Proof of the Backup Is in the Pudding</a> first appeared on <a href="https://marlonribunal.com">SQL, Code, Coffee, Etc.</a>.</p>]]></description>
										<content:encoded><![CDATA[<p class="wp-block-paragraph">Sometimes, a simple comment on LinkedIn gives you an idea worth writing about.</p>



<p class="wp-block-paragraph">After sharing my <a href="https://www.linkedin.com/feed/update/urn:li:activity:7522662489344491520/" target="_blank" rel="noopener nofollow" title="Marlon Ribunal's thought on SQL Server Backups">thoughts on SQL Server native backups</a> using Ola Hallengren&#8217;s Maintenance Solution, Mark Gribler left a comment that caught my attention:</p>



<p class="wp-block-paragraph"><strong>&#8220;The proof of a backup is a restore&#8221; (apologies to puddings)!!</strong></p>



<p class="wp-block-paragraph">I had to smile at that one.</p>



<p class="wp-block-paragraph">It&#8217;s a clever play on the old saying, &#8220;The proof of the pudding is in the eating.&#8221; And the more I thought about it, the more I realized how perfectly it describes what a good SQL Server backup strategy should be.</p>



<p class="wp-block-paragraph">You can have a backup job that runs every night, reports success, sends you an email notification, and gives you a nice green checkmark on your monitoring dashboard. But until you have successfully restored that backup, what exactly have you proven?</p>



<p class="wp-block-paragraph">Mark&#8217;s comment gave me the idea for this blog post.</p>



<p class="wp-block-paragraph">My original LinkedIn post questioned why some people consider native SQL Server backups old-fashioned, particularly when there are plenty of modern third-party backup products available today.</p>



<p class="wp-block-paragraph">Apparently, I touched a nerve or two.</p>



<p class="wp-block-paragraph">The discussion brought some interesting responses. Quite a few DBAs shared their confidence in Ola&#8217;s solution, while others shared less favorable experiences with third-party backup products.</p>



<p class="wp-block-paragraph">But regardless of which side of the discussion you belong to, I think we can agree on one thing:</p>



<p class="wp-block-paragraph"><strong>A backup is only as good as your ability to restore it.</strong></p>



<h2 class="wp-block-heading">A successful backup is only half the story</h2>



<p class="wp-block-paragraph">As DBAs, we spend a lot of time making sure backups are running as scheduled. We configure full, differential, and transaction log backups. We monitor job history, check backup sizes, review failures, and make sure backup files are being written to their intended destinations.</p>



<p class="wp-block-paragraph">All of that is important.</p>



<p class="wp-block-paragraph">But there is another question we should be asking:</p>



<p class="wp-block-paragraph"><strong>Have we actually restored those backups?</strong></p>



<p class="wp-block-paragraph">A backup job reporting success doesn&#8217;t automatically mean you have a working recovery strategy.</p>



<p class="wp-block-paragraph">The backup file might be inaccessible when you need it. The storage location might be unavailable. You might discover that the backup chain is incomplete, or that the process of restoring the database takes considerably longer than expected.</p>



<p class="wp-block-paragraph">And then there&#8217;s the possibility that nobody has actually tested the recovery procedure.</p>



<p class="wp-block-paragraph">Imagine being in the middle of a production incident, with management asking how long it will take to bring the database back online, only to discover that the backup process you&#8217;ve trusted for months has never been tested through an actual restore.</p>



<p class="wp-block-paragraph">That&#8217;s a situation I&#8217;d rather avoid.</p>



<h2 class="wp-block-heading">Why I still like Ola Hallengren&#8217;s Maintenance Solution</h2>



<p class="wp-block-paragraph">I&#8217;ve been a fan of <a href="https://ola.hallengren.com/" target="_blank" rel="noopener nofollow">Ola Hallengren&#8217;s Maintenance Solution</a> for a long time, particularly its backup component.</p>



<p class="wp-block-paragraph">It is mature, well-established, widely used, and does what it is supposed to do.</p>



<p class="wp-block-paragraph">One thing I appreciate about it is its simplicity. Ola&#8217;s backup solution provides a consistent and configurable way of executing SQL Server&#8217;s native backup commands. It handles the scheduling, backup file naming, retention, cleanup, and other operational details that DBAs need to manage.</p>



<p class="wp-block-paragraph">Underneath it, SQL Server is still doing the actual backup work.</p>



<p class="wp-block-paragraph">The resulting backup is a native SQL Server backup. You don&#8217;t need Ola&#8217;s Maintenance Solution installed to restore a database backed up through it. You can use SQL Server Management Studio, T-SQL, or other supported restore methods.</p>



<p class="wp-block-paragraph">For example:</p>



<pre class="wp-block-code"><code>EXECUTE dbo.DatabaseBackup
    @Databases = 'MyDatabase',
    @Directory = 'D:\SQLBackups',
    @BackupType = 'FULL',
    @Verify = 'Y',
    @Compress = 'Y',
    @CheckSum = 'Y',
    @LogToTable = 'Y';</code></pre>



<p class="wp-block-paragraph">And when it comes to restoring:</p>



<pre class="wp-block-code"><code>RESTORE DATABASE &#91;MyDatabase]
FROM DISK = 'D:\SQLBackups\MyDatabase.bak'
WITH CHECKSUM, STATS = 10;</code></pre>



<p class="wp-block-paragraph">Of course, these are simplified examples. A real recovery procedure needs to account for the backup chain, recovery model, file locations, database state, and other requirements.</p>



<p class="wp-block-paragraph">But that&#8217;s part of what I like about this approach. The backup and restore process uses capabilities that are already part of SQL Server.</p>



<p class="wp-block-paragraph">There is no additional backup engine that I need to understand before I can recover a database.</p>



<p class="wp-block-paragraph">I&#8217;m not saying Ola&#8217;s solution is the only way to back up SQL Server. I&#8217;m saying it is a proven and practical option that continues to serve its purpose very well.</p>



<h2 class="wp-block-heading">Do we really need another layer of complexity?</h2>



<p class="wp-block-paragraph">This is where I become a little more cautious about third-party backup products.</p>



<p class="wp-block-paragraph">Don&#8217;t get me wrong. There are legitimate reasons to use them.</p>



<p class="wp-block-paragraph">Organizations may have centralized backup requirements, enterprise retention policies, offsite replication, immutable storage, reporting, or backup management across different platforms. A third-party product may address requirements that go beyond simply backing up SQL Server databases.</p>



<p class="wp-block-paragraph">That&#8217;s perfectly reasonable.</p>



<p class="wp-block-paragraph">However, I sometimes wonder whether we introduce more complexity than necessary when choosing a backup product.</p>



<p class="wp-block-paragraph">Some products integrate deeply with SQL Server, while others introduce their own management layers, agents, processes, and recovery dependencies.</p>



<p class="wp-block-paragraph">The concern isn&#8217;t necessarily how the backup is taken. It&#8217;s what happens when you need to restore it.</p>



<p class="wp-block-paragraph">Do you need the same third-party software to perform the restore? Does it require a particular version of the product? What happens if the backup server is unavailable? What if the product license has expired, or the organization no longer has access to the software?</p>



<p class="wp-block-paragraph">Can you restore a database without having to go through several layers of infrastructure and dependencies?</p>



<p class="wp-block-paragraph">These are questions worth asking before committing to a backup product.</p>



<p class="wp-block-paragraph">I&#8217;ve seen discussions from DBAs who have experienced limitations with third-party backup solutions, particularly when it comes to restoring databases or performing more specific recovery operations.</p>



<p class="wp-block-paragraph">And that&#8217;s something worth considering.</p>



<p class="wp-block-paragraph">SQL Server has several recovery capabilities, including point-in-time recovery, file and filegroup restores, and page restores where supported. Your backup strategy and chosen tools should support the recovery scenarios your environment actually requires.</p>



<p class="wp-block-paragraph">Having a product that can report successful backups across hundreds of servers is useful. Having one that can reliably get your databases back when things go wrong is far more important.</p>



<h2 class="wp-block-heading">Old doesn&#8217;t necessarily mean ineffective</h2>



<p class="wp-block-paragraph">Another thing that came out of the LinkedIn discussion was the recurring perception that native SQL Server backups are somehow outdated.</p>



<p class="wp-block-paragraph">I don&#8217;t quite understand that argument.</p>



<p class="wp-block-paragraph">Just because something has been around for a long time doesn&#8217;t mean it has stopped being effective.</p>



<p class="wp-block-paragraph">SQL Server&#8217;s native backup and restore capabilities have been around for decades. Microsoft continues to support and improve them. Ola Hallengren&#8217;s Maintenance Solution has also been around for years, and it continues to be maintained and used by DBAs around the world.</p>



<p class="wp-block-paragraph">Why replace something that works simply because something newer is available?</p>



<p class="wp-block-paragraph">I&#8217;m all for modern tools and technologies. They have their place, and I don&#8217;t think we should dismiss them just because they come from a third party.</p>



<p class="wp-block-paragraph">But newer doesn&#8217;t automatically mean better. More features don&#8217;t necessarily mean a better recovery process. And a more sophisticated backup dashboard doesn&#8217;t guarantee that your database can be restored.</p>



<p class="wp-block-paragraph">Sometimes, a straightforward and well-understood approach is exactly what you need.</p>



<h2 class="wp-block-heading">Test your backups. Actually restore them.</h2>



<p class="wp-block-paragraph">If there&#8217;s one thing I&#8217;d like DBAs to take away from this discussion, it&#8217;s that backup monitoring should not stop at checking whether a job completed successfully.</p>



<p class="wp-block-paragraph">We should also have a process for regularly testing restores.</p>



<p class="wp-block-paragraph">A few things I&#8217;d want to see in a SQL Server backup and recovery routine:</p>



<ul class="wp-block-list">
<li><strong>Regular restore testing.</strong> Restore production backups to an isolated environment. Don&#8217;t just assume that a successful backup job means everything is fine.</li>



<li><strong>Backup integrity checks.</strong> Use backup checksums and appropriate verification procedures. <code>RESTORE VERIFYONLY</code> can provide an additional check, but it is <a href="https://marlonribunal.com/your-sql-server-database-just-failed-can-you-restore-the-backup/" target="_blank" rel="noopener nofollow">not a substitute for performing an actual restore</a>.</li>



<li><strong>Recovery time validation.</strong> Know how long it takes to restore your databases. A technically successful restore that takes 20 hours when the business expects recovery within two hours is still a problem.</li>



<li><strong>Point-in-time recovery testing.</strong> Make sure your full, differential, and transaction log backups work together as expected.</li>



<li><strong>Documented recovery procedures.</strong> Know where the backups are, what dependencies are involved, and who can perform the restore.</li>
</ul>



<p class="wp-block-paragraph">I would also include system databases and other instance-level dependencies in the overall disaster recovery plan. Restoring a user database is one thing. Recovering an entire SQL Server environment is another.</p>



<p class="wp-block-paragraph">The important thing is to make recovery testing part of the routine, not something you figure out for the first time during an emergency.</p>



<p class="wp-block-paragraph">I don&#8217;t have anything against third-party backup products. If they solve a real business requirement and provide a reliable recovery process, by all means, use them.</p>



<p class="wp-block-paragraph">But I wouldn&#8217;t dismiss native SQL Server backups or Ola Hallengren&#8217;s Maintenance Solution simply because they aren&#8217;t the latest products on the market.</p>



<p class="wp-block-paragraph">For me, the objective is straightforward: have a backup strategy that is reliable, understandable, maintainable, and, most importantly, restorable.</p>



<p class="wp-block-paragraph">A successful backup job is good news. A successful restore is proof that your backup strategy actually works.</p>



<p class="wp-block-paragraph">So the next time your backup job reports success, don&#8217;t just celebrate the green checkmark.</p>



<p class="wp-block-paragraph"><strong>Restore it. Test it. Prove it.</strong></p>



<p class="wp-block-paragraph">Because the proof of the backup is in the pudding!</p>



<p class="wp-block-paragraph">And in our world, the pudding is the restore.</p>



<p class="wp-block-paragraph"><em>And thanks to Mark Gibler for the inspiration. I think he put it better than I could have: the proof of a backup is a restore.</em></p>



<p class="wp-block-paragraph"></p><p>The post <a href="https://marlonribunal.com/the-proof-of-the-backup-is-in-the-pudding/">The Proof of the Backup Is in the Pudding</a> first appeared on <a href="https://marlonribunal.com">SQL, Code, Coffee, Etc.</a>.</p>]]></content:encoded>
					
					<wfw:commentRss>https://marlonribunal.com/the-proof-of-the-backup-is-in-the-pudding/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
		<item>
		<title>SQL Server Problems You Can Reproduce, Measure and Fix: A Free Demo Library</title>
		<link>https://marlonribunal.com/sql-server-demos-library/</link>
					<comments>https://marlonribunal.com/sql-server-demos-library/#respond</comments>
		
		<dc:creator><![CDATA[Marlon Ribunal]]></dc:creator>
		<pubDate>Thu, 29 Oct 2026 13:00:00 +0000</pubDate>
				<category><![CDATA[SQL Server]]></category>
		<category><![CDATA[SQLServerPedia Syndication]]></category>
		<category><![CDATA[Tools]]></category>
		<category><![CDATA[performance tuning]]></category>
		<category><![CDATA[SQL Server 2022]]></category>
		<category><![CDATA[tsql]]></category>
		<guid isPermaLink="false">https://marlonribunal.com/?p=3082</guid>

					<description><![CDATA[<p>I built a free library of runnable SQL Server demos. Each reproduces a real production problem on purpose, measures the fixes, and checks its own predictions on SQL Server 2019, 2022 and 2025. <a href="https://marlonribunal.com/sql-server-demos-library/">Continue reading <span class="meta-nav">&#8594;</span></a></p>
<p>The post <a href="https://marlonribunal.com/sql-server-demos-library/">SQL Server Problems You Can Reproduce, Measure and Fix: A Free Demo Library</a> first appeared on <a href="https://marlonribunal.com">SQL, Code, Coffee, Etc.</a>.</p>]]></description>
										<content:encoded><![CDATA[<p class="wp-block-paragraph"><em>A note on how this was made: I built these demos and explainers with the help of AI. Every script runs against real SQL Server instances, checks its own predictions, and is re-run by continuous integration on SQL Server 2019, 2022 and 2025, so the numbers here come from those runs.</em></p>



<p class="wp-block-paragraph">Most SQL Server advice arrives as a rule: don&#8217;t use <code>NOLOCK</code>, rebuild indexes over 30% fragmentation, make every string <code>nvarchar(max)</code> because storage is the same anyway. Some of those rules are right, some are half right, and a few are wrong in ways that only show up under load.</p>



<p class="wp-block-paragraph">I wanted to stop repeating rules and start showing evidence. So I built <strong><a href="https://github.com/MarlonRibunal/sqlserver-demos">SQL Server Demos</a></strong>: a free, open-source library of runnable demos. Each one reproduces a real production problem on purpose, measures every common fix, and checks its own predictions. Every topic also has a short explainer here on the blog, in the <strong><a href="/sqlserver-demos/">SQL Server Demos library</a></strong>.</p>



<h2 class="wp-block-heading">What&#8217;s in the library</h2>



<p class="wp-block-paragraph">The demos are organised around the symptom you&#8217;re seeing, not the feature name, because that&#8217;s how problems arrive in production:</p>



<ul class="wp-block-list">
<li><strong>&#8220;It&#8217;s fast sometimes and slow other times&#8221;</strong>: <a href="/sqlserver-demos/parameter-sniffing/">parameter sniffing</a>, <a href="/sqlserver-demos/slow-in-app-fast-in-ssms/">slow in the app, fast in SSMS</a>, <a href="/sqlserver-demos/catch-all-queries/">catch-all queries</a>, <a href="/sqlserver-demos/query-store-regression/">Query Store plan regressions</a></li>


<li><strong>&#8220;This query reads far more than it should&#8221;</strong>: <a href="/sqlserver-demos/non-sargable-predicates/">non-SARGable predicates</a>, <a href="/sqlserver-demos/implicit-conversion/">implicit conversions</a>, <a href="/sqlserver-demos/tipping-point/">key lookups and the tipping point</a>, <a href="/sqlserver-demos/partition-elimination/">partition elimination</a></li>


<li><strong>&#8220;The estimates are nowhere near the actual rows&#8221;</strong>: <a href="/sqlserver-demos/ascending-key/">the ascending-key problem</a>, <a href="/sqlserver-demos/correlated-predicates/">correlated predicates</a>, <a href="/sqlserver-demos/statistics-sampling/">statistics sampling</a></li>


<li><strong>&#8220;Everything is blocked&#8221; or &#8220;we get deadlocks&#8221;</strong>: <a href="/sqlserver-demos/blocking-chains/">blocking chains</a>, <a href="/sqlserver-demos/deadlock-patterns/">deadlock patterns</a>, <a href="/sqlserver-demos/lock-escalation/">lock escalation</a>, <a href="/sqlserver-demos/rcsi-snapshot-isolation/">RCSI and snapshot isolation</a></li>


<li><strong>&#8220;The server is slow and I don&#8217;t know where to start&#8221;</strong>: <a href="/sqlserver-demos/wait-stats-triage/">wait stats triage</a>, <a href="/sqlserver-demos/parallelism/">parallelism and CXPACKET</a></li>


<li><strong>&#8220;The transaction log is full&#8221;</strong>: <a href="/sqlserver-demos/transaction-log-full/">why is my transaction log full?</a>, <a href="/sqlserver-demos/minimal-logging/">minimal logging</a>, <a href="/sqlserver-demos/backup-restore/">backup and restore</a></li>


<li><strong>What&#8217;s new in SQL Server 2022 and 2025</strong>: <a href="/sqlserver-demos/sql2022-iqp/">parameter-sensitive plans and feedback</a>, <a href="/sqlserver-demos/optimized-locking/">optimized locking</a>, <a href="/sqlserver-demos/optional-parameter-plans/">optional parameter plan optimization</a></li>
</ul>



<p class="wp-block-paragraph">The full list is on the <a href="/sqlserver-demos/">library page</a>.</p>



<h2 class="wp-block-heading">A few things the demos measured</h2>



<p class="wp-block-paragraph">The point of running the demos rather than reading about them is that the numbers sometimes disagree with the folklore:</p>



<ul class="wp-block-list">
<li><strong><code>NOLOCK</code> read a balance that never existed.</strong> The writer rolled back, and the reader had already returned the uncommitted value. RCSI returned the last committed value with no wait at all. (<a href="/sqlserver-demos/rcsi-snapshot-isolation/">RCSI and snapshot isolation</a>)</li>


<li><strong>A 99.97% fragmented index did exactly the same reads as a clean one</strong>, to the page. Half-empty pages, at 0.12% fragmentation, doubled the reads. (<a href="/sqlserver-demos/index-fragmentation/">index fragmentation</a>)</li>


<li><strong><code>varchar(4000)</code> holding 17-character names was granted 1.4 GB of memory</strong> for a sort that used 24 MB. <code>varchar(50)</code> was granted 68 MB. (<a href="/sqlserver-demos/memory-grant-declared-width/">memory grants</a>)</li>


<li><strong>Page 1,000 with <code>OFFSET ... FETCH</code> took 159,530 reads.</strong> Keyset paging took 217, on every page. (<a href="/sqlserver-demos/pagination/">pagination</a>)</li>


<li><strong><code>IF EXISTS ... INSERT</code> produced 598 primary key violations in 800 upserts</strong> under concurrency. <code>UPDLOCK, SERIALIZABLE</code> produced none. (<a href="/sqlserver-demos/upsert-race-conditions/">upsert race conditions</a>)</li>


<li><strong>On SQL Server 2025, the classic catch-all search</strong> dropped from 3,001,752 reads to 16,286 at compatibility level 170, but two optional parameters can still reuse a bad plan. (<a href="/sqlserver-demos/optional-parameter-plans/">optional parameter plans</a>)</li>
</ul>



<h2 class="wp-block-heading">How the demos are built</h2>



<p class="wp-block-paragraph">Every topic follows the same shape, so once you&#8217;ve run one you can run them all:</p>



<ol class="wp-block-list">
<li><code>01-setup.sql</code> builds the data, usually in a database of its own.</li>


<li><code>02-demo.sql</code> runs the whole demonstration unattended and captures its own evidence.</li>


<li><code>03-cleanup.sql</code> puts back anything setup changed and drops everything.</li>
</ol>



<p class="wp-block-paragraph">Each demo ends with a result set listing <strong>anything that didn&#8217;t behave as predicted</strong>. Continuous integration runs every topic on <strong>SQL Server 2019, 2022 and 2025</strong> on every push, so a passing run means the behaviour described really happened on that version, not just that the script finished.</p>



<p class="wp-block-paragraph">They&#8217;re also written to be safe on a shared instance. Nothing flushes the whole plan cache or clears instance-wide wait stats, and setup records every setting it changes so cleanup can restore it. They&#8217;re still demos, though: run them on a scratch instance. A <code>docker-compose.yml</code> in the repo starts SQL Server 2019, 2022 and 2025 side by side.</p>



<h2 class="wp-block-heading">Each explainer is a one-page answer</h2>



<p class="wp-block-paragraph">The <a href="/sqlserver-demos/">explainers</a> are short reference pages, not essays. Each one covers:</p>



<ul class="wp-block-list">
<li><strong>What you&#8217;ll see</strong>: the symptom, in the words you&#8217;d search for</li>


<li><strong>Why it happens</strong></li>


<li><strong>What to do</strong>, and <strong>what doesn&#8217;t help</strong></li>


<li><strong>Check your server</strong>: a read-only query to run on your own instance</li>


<li><strong>Run it yourself</strong>: a link to the demo on GitHub</li>
</ul>



<p class="wp-block-paragraph">Every page also has a short link, such as <code>marlonribunal.com/go/parameter-sniffing</code>, to paste into a ticket or a chat.</p>



<h2 class="wp-block-heading">Try it</h2>



<ul class="wp-block-list">
<li><strong>Browse the explainers:</strong> <a href="/sqlserver-demos/">marlonribunal.com/sqlserver-demos</a></li>


<li><strong>Get the scripts:</strong> <a href="https://github.com/MarlonRibunal/sqlserver-demos">github.com/MarlonRibunal/sqlserver-demos</a></li>


<li><strong>Found a demo that didn&#8217;t behave as described?</strong> <a href="https://github.com/MarlonRibunal/sqlserver-demos/issues/new/choose">Open an issue</a>. That&#8217;s exactly the kind of report I want.</li>
</ul>



<p class="wp-block-paragraph">If the library helps you, a star on GitHub or a share with your team helps other people find it.</p>



<h2 class="wp-block-heading">Frequently asked questions</h2>



<h3 class="wp-block-heading">Are the SQL Server demos free?</h3>



<p class="wp-block-paragraph">Yes. The scripts are MIT-licensed on GitHub, and the explainers are free to read.</p>



<h3 class="wp-block-heading">Which SQL Server versions do the demos support?</h3>



<p class="wp-block-paragraph">Continuous integration runs every demo on SQL Server 2019, 2022 and 2025. Demos for newer features report <code>SKIPPED</code> on older versions instead of failing. Azure SQL Database and Managed Instance haven&#8217;t been tested.</p>



<h3 class="wp-block-heading">Can I run the demos on a production server?</h3>



<p class="wp-block-paragraph">No. Several demos change database settings by design. Run them on a scratch instance; the repo&#8217;s <code>docker-compose.yml</code> starts one in a minute.</p>



<h3 class="wp-block-heading">Do I need a sample database?</h3>



<p class="wp-block-paragraph">Only the parameter sniffing demo needs WideWorldImporters. The others create their own data.</p><p>The post <a href="https://marlonribunal.com/sql-server-demos-library/">SQL Server Problems You Can Reproduce, Measure and Fix: A Free Demo Library</a> first appeared on <a href="https://marlonribunal.com">SQL, Code, Coffee, Etc.</a>.</p>]]></content:encoded>
					
					<wfw:commentRss>https://marlonribunal.com/sql-server-demos-library/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
		<item>
		<title>Book Review: Microsoft 365 Copilot and Agent Administration Fundamentals</title>
		<link>https://marlonribunal.com/book-review-microsoft-365-copilot-and-agent-administration-fundamentals/</link>
					<comments>https://marlonribunal.com/book-review-microsoft-365-copilot-and-agent-administration-fundamentals/#respond</comments>
		
		<dc:creator><![CDATA[Marlon Ribunal]]></dc:creator>
		<pubDate>Fri, 23 Oct 2026 11:30:00 +0000</pubDate>
				<category><![CDATA[Review]]></category>
		<category><![CDATA[SQL Server]]></category>
		<guid isPermaLink="false">https://marlonribunal.com/?p=2995</guid>

					<description><![CDATA[<p>I don’t currently manage Microsoft 365 Copilot in an enterprise environment, but it is one of those technologies that I want to understand better. As AI becomes part of the tools organizations use every day, there is more to learn &#8230; <a href="https://marlonribunal.com/book-review-microsoft-365-copilot-and-agent-administration-fundamentals/">Continue reading <span class="meta-nav">&#8594;</span></a></p>
<p>The post <a href="https://marlonribunal.com/book-review-microsoft-365-copilot-and-agent-administration-fundamentals/">Book Review: Microsoft 365 Copilot and Agent Administration Fundamentals</a> first appeared on <a href="https://marlonribunal.com">SQL, Code, Coffee, Etc.</a>.</p>]]></description>
										<content:encoded><![CDATA[<p class="wp-block-paragraph">I don’t currently manage Microsoft 365 Copilot in an enterprise environment, but it is one of those technologies that I want to understand better. As AI becomes part of the tools organizations use every day, there is more to learn than just how to use Copilot. </p>


<div class="wp-block-image">
<figure class="alignleft size-large is-resized"><a href="https://www.amazon.com/Microsoft-Copilot-Agent-Administration-Fundamentals/dp/1807306518/"><img decoding="async" src="https://m.media-amazon.com/images/I/715m4A0qIhL._SL1500_.jpg" alt="" style="aspect-ratio:0.8106763175752092;width:218px;height:auto"/></a></figure>
</div>


<p class="wp-block-paragraph">Someone has to manage access, understand licensing, protect company data, and make sure these tools are being used appropriately. And if I ever find myself responsible for that side of things, I want to have a good foundation to start with.</p>



<p class="wp-block-paragraph">That is where Steve Miles’ <em>Microsoft 365 Copilot and Agent Administration Fundamentals</em>, published by Packt, comes in.</p>



<p class="wp-block-paragraph">The book covers quite a bit of ground, starting with the fundamentals of Microsoft 365 administration before moving into security, data protection, Copilot, and AI agents. It also prepares readers for the Microsoft AB-900 certification exam.</p>



<h2 class="wp-block-heading">Understanding What Happens Behind the Scenes</h2>



<p class="wp-block-paragraph">One thing I appreciate about the book is that it starts with the basics. Before getting into Copilot administration, you need to understand the Microsoft 365 environment in which it operates. This includes identity, licensing, permissions, and the different services that make up Microsoft 365.</p>



<p class="wp-block-paragraph">Some of these topics may already be familiar to IT professionals who work with Microsoft 365 regularly. For others, particularly those coming from a different area of IT, having these concepts explained in one place can be useful.</p>



<p class="wp-block-paragraph">The security and data protection chapters are especially relevant. Copilot works with organizational data, so understanding how permissions affect what users can access is important. The discussions around Microsoft Purview, data governance, and oversharing in SharePoint help explain why deploying AI tools in an organization requires more thought than simply enabling a feature and giving users access.</p>



<p class="wp-block-paragraph">This is probably one of the areas I find most interesting. We often talk about what AI can do, but there is another side to the conversation. What information can it access? Are existing permissions appropriate? What happens when sensitive information is exposed to people who should not have access to it? These are questions administrators need to consider before rolling out these tools.</p>



<h2 class="wp-block-heading">Copilot and Agents Administration</h2>



<p class="wp-block-paragraph">The later chapters get into the administration of Copilot and agents, including licensing, usage monitoring, billing, access control, approval processes, and lifecycle management.</p>



<p class="wp-block-paragraph">I like that the book covers these operational considerations alongside the features themselves. Understanding what Copilot and agents can do is one thing. Knowing how to manage them within an organization is another.</p>



<p class="wp-block-paragraph">The sections on creating, testing, approving, and monitoring agents are particularly useful for anyone looking to understand how these tools fit into an organization&#8217;s existing environment. There is also value in learning how licensing and access restrictions affect what users can actually do.</p>



<p class="wp-block-paragraph">Of course, reading about these administrative tasks is different from performing them in a live tenant. I would still want to get hands-on experience with the relevant admin centers and settings to reinforce what I have learned. But having the concepts laid out first gives me a much better starting point.</p>



<h2 class="wp-block-heading">A Useful Learning Resource</h2>



<p class="wp-block-paragraph">Another thing I appreciate about technical books is having the material organized into chapters that I can revisit when needed. Online documentation is valuable, especially when looking for current configuration details, but sometimes I want a structured path through a subject before diving into individual features.</p>



<p class="wp-block-paragraph">The book includes chapter summaries, key terms, Microsoft Learn references, and review questions. These are useful for reinforcing the material and preparing for the AB-900 exam. The exam-oriented approach also gives readers a way to check their understanding as they progress.</p>



<p class="wp-block-paragraph">One limitation worth mentioning is that this is a fundamentals book. Readers looking for extensive, real-world deployment walkthroughs or advanced troubleshooting scenarios may need to supplement it with hands-on practice and Microsoft&#8217;s documentation. Given the breadth of topics covered, there is only so much detail that can fit into a single book.</p>



<p class="wp-block-paragraph">Still, I think that is a reasonable trade-off for a resource intended to establish a foundation across Microsoft 365, security, Copilot, and agents.</p>



<h2 class="wp-block-heading">Final Thoughts</h2>



<p class="wp-block-paragraph">Microsoft 365 Copilot and Agent Administration Fundamentals by Steve Miles is a useful addition to the technical bookshelf, especially for IT professionals who want to expand their knowledge beyond the technologies they currently manage.</p>



<p class="wp-block-paragraph">I may not be administering Copilot in an enterprise environment today, but I can see the value of understanding what goes into managing it properly. If that responsibility comes my way in the future, I will have a starting point and a better idea of what I need to learn next.</p>



<p class="wp-block-paragraph">And even if you are already working with Microsoft 365, the book offers a structured way to review the fundamentals and connect them to the administration of Copilot and AI agents.</p>



<p class="wp-block-paragraph">That alone makes it a worthwhile read for anyone looking to get a better grasp of this part of the Microsoft ecosystem.</p><p>The post <a href="https://marlonribunal.com/book-review-microsoft-365-copilot-and-agent-administration-fundamentals/">Book Review: Microsoft 365 Copilot and Agent Administration Fundamentals</a> first appeared on <a href="https://marlonribunal.com">SQL, Code, Coffee, Etc.</a>.</p>]]></content:encoded>
					
					<wfw:commentRss>https://marlonribunal.com/book-review-microsoft-365-copilot-and-agent-administration-fundamentals/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
		<item>
		<title>Creating a Custom SQL Server Security Checklist Using the DoD STIG</title>
		<link>https://marlonribunal.com/creating-a-custom-sql-server-security-checklist-using-the-dod-stig/</link>
					<comments>https://marlonribunal.com/creating-a-custom-sql-server-security-checklist-using-the-dod-stig/#comments</comments>
		
		<dc:creator><![CDATA[Marlon Ribunal]]></dc:creator>
		<pubDate>Tue, 22 Sep 2026 11:30:00 +0000</pubDate>
				<category><![CDATA[SQL Server]]></category>
		<guid isPermaLink="false">https://marlonribunal.com/?p=2973</guid>

					<description><![CDATA[<p>The STIG is detailed, which is a good thing, but I found myself wanting something a little more practical for day-to-day DBA work. Something I could open, work through one item at a time, record what I found, and come back to later without having to navigate through the entire STIG document every time.</p>
<p>That led me to the idea of creating my own SQL Server security checklist. <a href="https://marlonribunal.com/creating-a-custom-sql-server-security-checklist-using-the-dod-stig/">Continue reading <span class="meta-nav">&#8594;</span></a></p>
<p>The post <a href="https://marlonribunal.com/creating-a-custom-sql-server-security-checklist-using-the-dod-stig/">Creating a Custom SQL Server Security Checklist Using the DoD STIG</a> first appeared on <a href="https://marlonribunal.com">SQL, Code, Coffee, Etc.</a>.</p>]]></description>
										<content:encoded><![CDATA[<p class="wp-block-paragraph">Here&#8217;s a follow up for our US Department of Defense STIG document. In my previous post, <a href="https://marlonribunal.com/sql-server-security-hardening-guide-using-the-dod-stig-checklist/" title="">SQL Server Security Hardening Guide Using the DoD STIG Checklist</a>, I walked through how I used the DoD STIG checklist as a starting point for reviewing and hardening a SQL Server environment.</p>



<p class="wp-block-paragraph">After going through the checklist, I started thinking about what I would actually want to use the next time I perform a security review.</p>



<p class="wp-block-paragraph">The DoD STIG for SQL Server is a great, solid starting point for establishing your security practices with SQL Server. In fact, it&#8217;s also a good template for your own STIG in your organization. So, you may want to create a custom checklist that makes sense from the perspective of your SQL Server environment.</p>



<p class="wp-block-paragraph">The STIG is detailed, which is a good thing, but I found myself wanting something a little more practical for day-to-day DBA work. Something I could open, work through one item at a time, record what I found, and come back to later without having to navigate through the entire STIG document every time.</p>



<h2 class="wp-block-heading">Questions to Ask</h2>



<p class="wp-block-paragraph">I want it to answer some simple questions:</p>



<ul class="wp-block-list">
<li>What am I checking?</li>



<li>Why am I checking it?</li>



<li>How can I verify it?</li>



<li>What does PASS or FAIL look like?</li>



<li>What evidence should I record?</li>



<li>Does this requirement actually apply to this environment?</li>



<li>If I can&#8217;t meet a requirement, how do I document the exception?</li>
</ul>



<p class="wp-block-paragraph">So in this post, I&#8217;ll walk through how I&#8217;m building the checklist, based on the DoD STIG as the baseline (and I can then organize it into something I can actually use as a DBA).</p>



<p class="wp-block-paragraph">The main thing here is to <strong>understand what the STIG is asking you to verify</strong>.</p>



<p class="wp-block-paragraph">Once I have the STIG requirements in front of me, the next step is to break each rule down into information that I can actually work with. Rather than simply copying the requirement into my checklist, I want to capture a few key details for each rule. </p>



<p class="wp-block-paragraph">This gives me enough information to understand what I&#8217;m checking, how I can validate it, and what I should record when I&#8217;m done.</p>



<p class="wp-block-paragraph">Again, this STIG is just a starting point. Capture the checklist in a separate document that you can share in your organization.</p>



<h2 class="wp-block-heading">What to Capture?</h2>



<p class="wp-block-paragraph">For every rule, capture:</p>



<ul class="wp-block-list">
<li>STIG ID</li>



<li>Severity</li>



<li>Requirement</li>



<li>Check</li>



<li>Fix</li>



<li>Instance or Database</li>



<li>Applicable?</li>



<li>Current status</li>
</ul>



<h2 class="wp-block-heading">Let&#8217;s Create a Checklist</h2>



<p class="wp-block-paragraph">Let&#8217;s open the STIG Viewer, at the <strong>Checklist </strong>section, click New to create a new checklist.</p>



<p class="wp-block-paragraph"></p>



<figure class="wp-block-image size-large"><img decoding="async" width="1024" height="747" src="https://marlonribunal.com/wp-content/uploads/2026/09/image-1024x747.png" alt="" class="wp-image-2974" srcset="https://marlonribunal.com/wp-content/uploads/2026/09/image-1024x747.png 1024w, https://marlonribunal.com/wp-content/uploads/2026/09/image-300x219.png 300w, https://marlonribunal.com/wp-content/uploads/2026/09/image-767x560.png 767w, https://marlonribunal.com/wp-content/uploads/2026/09/image-1536x1121.png 1536w, https://marlonribunal.com/wp-content/uploads/2026/09/image-2048x1495.png 2048w" sizes="(max-width: 1024px) 100vw, 1024px" /></figure>



<p class="wp-block-paragraph"></p>



<p class="wp-block-paragraph">Let&#8217;s select to create a checklist for a SQL Server Instance.</p>



<p class="wp-block-paragraph"></p>



<figure class="wp-block-image size-large"><img decoding="async" width="1024" height="720" src="https://marlonribunal.com/wp-content/uploads/2026/09/image-1-1024x720.png" alt="" class="wp-image-2975" srcset="https://marlonribunal.com/wp-content/uploads/2026/09/image-1-1024x720.png 1024w, https://marlonribunal.com/wp-content/uploads/2026/09/image-1-300x211.png 300w, https://marlonribunal.com/wp-content/uploads/2026/09/image-1-767x539.png 767w, https://marlonribunal.com/wp-content/uploads/2026/09/image-1-1536x1079.png 1536w, https://marlonribunal.com/wp-content/uploads/2026/09/image-1-2048x1439.png 2048w" sizes="(max-width: 1024px) 100vw, 1024px" /></figure>



<p class="wp-block-paragraph"></p>



<p class="wp-block-paragraph">You have to options: Add individual rules or add all the rules in the STIG. Click the search icon to pick the individual rules or the plus sign to add all the rules. For the purpose of this blog post, let&#8217;s add few rules.</p>



<p class="wp-block-paragraph">Select the rule by clicking the <strong>Plus</strong> sign. Select all that you want added in your checklist.</p>



<p class="wp-block-paragraph"></p>



<figure class="wp-block-image size-large"><img loading="lazy" decoding="async" width="1024" height="723" src="https://marlonribunal.com/wp-content/uploads/2026/09/image-2-1024x723.png" alt="" class="wp-image-2976" srcset="https://marlonribunal.com/wp-content/uploads/2026/09/image-2-1024x723.png 1024w, https://marlonribunal.com/wp-content/uploads/2026/09/image-2-300x212.png 300w, https://marlonribunal.com/wp-content/uploads/2026/09/image-2-768x542.png 768w, https://marlonribunal.com/wp-content/uploads/2026/09/image-2-1536x1084.png 1536w, https://marlonribunal.com/wp-content/uploads/2026/09/image-2-2048x1445.png 2048w" sizes="auto, (max-width: 1024px) 100vw, 1024px" /></figure>



<p class="wp-block-paragraph"></p>



<p class="wp-block-paragraph">To save the checklist, navigate to the burger menu in the top left-hand corner and select <strong>Save</strong>. Give the checklist file an intuitive name.</p>



<p class="wp-block-paragraph"></p>



<figure class="wp-block-image size-large"><img loading="lazy" decoding="async" width="1024" height="719" src="https://marlonribunal.com/wp-content/uploads/2026/09/image-3-1024x719.png" alt="" class="wp-image-2977" srcset="https://marlonribunal.com/wp-content/uploads/2026/09/image-3-1024x719.png 1024w, https://marlonribunal.com/wp-content/uploads/2026/09/image-3-300x211.png 300w, https://marlonribunal.com/wp-content/uploads/2026/09/image-3-767x538.png 767w, https://marlonribunal.com/wp-content/uploads/2026/09/image-3-1536x1078.png 1536w, https://marlonribunal.com/wp-content/uploads/2026/09/image-3-2048x1437.png 2048w" sizes="auto, (max-width: 1024px) 100vw, 1024px" /></figure>



<p class="wp-block-paragraph"></p>



<p class="wp-block-paragraph">Once saved, you can close the checklist builder. The STIG Checklist options will then give you a couple of options to load or create another checklist. Let&#8217;s open the checklist that we just created.</p>



<p class="wp-block-paragraph"></p>



<figure class="wp-block-image size-large"><img loading="lazy" decoding="async" width="1024" height="721" src="https://marlonribunal.com/wp-content/uploads/2026/09/image-4-1024x721.png" alt="" class="wp-image-2978" srcset="https://marlonribunal.com/wp-content/uploads/2026/09/image-4-1024x721.png 1024w, https://marlonribunal.com/wp-content/uploads/2026/09/image-4-300x211.png 300w, https://marlonribunal.com/wp-content/uploads/2026/09/image-4-767x540.png 767w, https://marlonribunal.com/wp-content/uploads/2026/09/image-4-1536x1081.png 1536w, https://marlonribunal.com/wp-content/uploads/2026/09/image-4-2048x1441.png 2048w" sizes="auto, (max-width: 1024px) 100vw, 1024px" /></figure>



<p class="wp-block-paragraph"></p>



<p class="wp-block-paragraph">Review the checklist and check it against a specific instance or database that you want to assess. Here you can note the instance/database information and mark each rule with three statuses: </p>



<p class="wp-block-paragraph">Green Check Icon: <strong>Not a Finding</strong> (meaning instance/database pass the rule), </p>



<p class="wp-block-paragraph">Red Exclamation: <strong>Open</strong> (for further review), or </p>



<p class="wp-block-paragraph">Crossed Circle: <strong>Not Applicable</strong></p>



<p class="wp-block-paragraph">Default Grey Circle: <strong>Not reviewed</strong></p>



<p class="wp-block-paragraph">Keep clicking the gray button to cycle through the statuses.</p>



<p class="wp-block-paragraph">You can also leave a comment and findings details in each of the rules in the designated boxes at the bottom.</p>



<p class="wp-block-paragraph"></p>



<figure class="wp-block-image size-large"><img loading="lazy" decoding="async" width="1024" height="716" src="https://marlonribunal.com/wp-content/uploads/2026/09/image-5-1024x716.png" alt="" class="wp-image-2979" srcset="https://marlonribunal.com/wp-content/uploads/2026/09/image-5-1024x716.png 1024w, https://marlonribunal.com/wp-content/uploads/2026/09/image-5-300x210.png 300w, https://marlonribunal.com/wp-content/uploads/2026/09/image-5-768x537.png 768w, https://marlonribunal.com/wp-content/uploads/2026/09/image-5-1536x1074.png 1536w, https://marlonribunal.com/wp-content/uploads/2026/09/image-5-2048x1432.png 2048w" sizes="auto, (max-width: 1024px) 100vw, 1024px" /></figure>



<p class="wp-block-paragraph"></p>



<p class="wp-block-paragraph">You can then export the checklist if you want to keep a separate file for the assessment (html and then print it to a pdf file).</p>



<p class="wp-block-paragraph"></p>



<figure class="wp-block-image size-large"><img loading="lazy" decoding="async" width="1024" height="716" src="https://marlonribunal.com/wp-content/uploads/2026/09/image-6-1024x716.png" alt="" class="wp-image-2980" srcset="https://marlonribunal.com/wp-content/uploads/2026/09/image-6-1024x716.png 1024w, https://marlonribunal.com/wp-content/uploads/2026/09/image-6-300x210.png 300w, https://marlonribunal.com/wp-content/uploads/2026/09/image-6-768x537.png 768w, https://marlonribunal.com/wp-content/uploads/2026/09/image-6-1536x1074.png 1536w, https://marlonribunal.com/wp-content/uploads/2026/09/image-6-2048x1432.png 2048w" sizes="auto, (max-width: 1024px) 100vw, 1024px" /></figure>



<p class="wp-block-paragraph"></p>



<p class="wp-block-paragraph">Here&#8217;s some screenshots of the  the example html&#8230;</p>



<p class="wp-block-paragraph"></p>



<figure class="wp-block-image size-large"><img loading="lazy" decoding="async" width="1024" height="751" src="https://marlonribunal.com/wp-content/uploads/2026/09/image-7-1024x751.png" alt="" class="wp-image-2981" srcset="https://marlonribunal.com/wp-content/uploads/2026/09/image-7-1024x751.png 1024w, https://marlonribunal.com/wp-content/uploads/2026/09/image-7-300x220.png 300w, https://marlonribunal.com/wp-content/uploads/2026/09/image-7-767x562.png 767w, https://marlonribunal.com/wp-content/uploads/2026/09/image-7-1536x1126.png 1536w, https://marlonribunal.com/wp-content/uploads/2026/09/image-7-2048x1501-1.png 2048w" sizes="auto, (max-width: 1024px) 100vw, 1024px" /></figure>



<figure class="wp-block-image size-large"><img loading="lazy" decoding="async" width="1024" height="746" src="https://marlonribunal.com/wp-content/uploads/2026/09/image-8-1024x746.png" alt="" class="wp-image-2982" srcset="https://marlonribunal.com/wp-content/uploads/2026/09/image-8-1024x746.png 1024w, https://marlonribunal.com/wp-content/uploads/2026/09/image-8-300x219.png 300w, https://marlonribunal.com/wp-content/uploads/2026/09/image-8-767x559.png 767w, https://marlonribunal.com/wp-content/uploads/2026/09/image-8-1536x1119.png 1536w, https://marlonribunal.com/wp-content/uploads/2026/09/image-8-2048x1493.png 2048w" sizes="auto, (max-width: 1024px) 100vw, 1024px" /></figure>



<p class="wp-block-paragraph"></p>



<h2 class="wp-block-heading">Your Checklist as Your Tool</h2>



<p class="wp-block-paragraph">Instead of reproducing the STIG&#8217;s structure, I&#8217;d create something a DBA can work through. I&#8217;d create a checklist for the following categories:</p>



<p class="wp-block-paragraph"></p>



<figure class="wp-block-table"><table class="has-fixed-layout"><thead><tr><th>Category</th><th>What you&#8217;re checking</th></tr></thead><tbody><tr><td>Authentication</td><td>How users authenticate</td></tr><tr><td>Authorization</td><td>Who has access to what</td></tr><tr><td>Accounts &amp; Logins</td><td>SQL logins, Windows accounts, disabled accounts</td></tr><tr><td>Privileges</td><td><code>sysadmin</code>, server roles, database roles</td></tr><tr><td>Auditing</td><td>Login and security-related auditing</td></tr><tr><td>Encryption</td><td>TDE, TLS, encryption at rest</td></tr><tr><td>Network Security</td><td>SQL ports, protocols, exposure</td></tr><tr><td>Configuration</td><td>SQL Server security-related configuration</td></tr><tr><td>Database Security</td><td>Database-level permissions and ownership</td></tr><tr><td>Service Accounts</td><td>SQL Server service identities</td></tr><tr><td>Agent Security</td><td>SQL Agent jobs, proxies, credentials</td></tr><tr><td>Sensitive Data</td><td>PII and other protected information</td></tr><tr><td>Monitoring</td><td>Security events and changes</td></tr><tr><td>Documentation</td><td>Exceptions, evidence and remediation</td></tr></tbody></table></figure>



<p class="wp-block-paragraph"></p>



<p class="wp-block-paragraph">That and among other things that may be applicable to whichever environment I happen to be working on.</p>



<p class="wp-block-paragraph">This is where your checklist becomes <strong>your own tool</strong>, rather than just another copy of the STIG.</p>



<p class="wp-block-paragraph"></p>



<h2 class="wp-block-heading">Most Important Thing, Document</h2>



<p class="wp-block-paragraph">This is an important part of the checklist. I don&#8217;t want the process to be simply about finding a problem and <strong>immediately changing the configuration</strong>. Involve everyone and, needless to say, document.</p>



<p class="wp-block-paragraph">The goal is to first understand the current state, evaluate whether the setting actually needs to be changed, make the appropriate remediation if necessary, and then validate the change. This gives me a more deliberate process instead of treating every finding as something that automatically requires a configuration change.</p>



<p class="wp-block-paragraph">This process would look as simple as the following:</p>



<p class="wp-block-paragraph"><strong>1. Check</strong> &#8211; Determine the current state.</p>



<p class="wp-block-paragraph"><strong>2. Evaluate</strong> &#8211; Decide whether the configuration is appropriate for your environment.</p>



<p class="wp-block-paragraph"><strong>3. Remediate</strong> &#8211; Make the change if necessary.</p>



<p class="wp-block-paragraph"><strong>4. Validate</strong> &#8211; Run the check again.</p>



<p class="wp-block-paragraph"><strong>5. Document</strong> &#8211; Record what changed.</p>



<p class="wp-block-paragraph">That gives you a repeatable process:</p>



<pre class="wp-block-preformatted"> <code>      CHECK
         ↓
      EVALUATE
         ↓
     REMEDIATE
         ↓
      VALIDATE
         ↓
     DOCUMENT</code></pre>



<p class="wp-block-paragraph">And I&#8217;d emphasize that <strong>STIG compliance doesn&#8217;t automatically mean every setting should simply be changed without considering the environment</strong>.</p>



<p class="wp-block-paragraph">If this was a real checklist for a SQL Server environment I am responsible for, this is my starting point. I expect the checklist to change as I use it, find gaps, and learn more about what works in an actual SQL Server environment. </p>



<p class="wp-block-paragraph">The STIG gives me a solid baseline, but turning those requirements into something I can consistently use as a DBA makes the exercise much more useful for me. </p>



<p class="wp-block-paragraph">My next step is to take these checks and start turning them into T-SQL scripts where possible, so instead of manually checking everything, I can let SQL Server help me identify what needs attention.</p>



<p class="wp-block-paragraph">Have fun and enjoy securing your SQL Server!</p><p>The post <a href="https://marlonribunal.com/creating-a-custom-sql-server-security-checklist-using-the-dod-stig/">Creating a Custom SQL Server Security Checklist Using the DoD STIG</a> first appeared on <a href="https://marlonribunal.com">SQL, Code, Coffee, Etc.</a>.</p>]]></content:encoded>
					
					<wfw:commentRss>https://marlonribunal.com/creating-a-custom-sql-server-security-checklist-using-the-dod-stig/feed/</wfw:commentRss>
			<slash:comments>1</slash:comments>
		
		
			</item>
	</channel>
</rss>