<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<title>Statistics on SQLSurfer</title>
		<link>http://localhost:1313/tags/statistics/</link>
		<description>Recent content in Statistics on SQLSurfer</description>
		<generator>Hugo</generator>
		<language>en-us</language>
		
		
		
		
			<lastBuildDate>Mon, 10 Aug 2026 18:00:20 -0500</lastBuildDate>
		
			<atom:link href="http://localhost:1313/tags/statistics/index.xml" rel="self" type="application/rss+xml" />
			<item>
				<title>Azure SQL Database - Index And Statistic Management</title>
				<link>http://localhost:1313/posts/azure-sql-database-index-and-statistic-management/</link>
				<pubDate>Mon, 10 Aug 2026 18:00:20 -0500</pubDate>
				<guid>http://localhost:1313/posts/azure-sql-database-index-and-statistic-management/</guid>
				<description>&lt;h2 id=&#34;dba-tasks-in-azure-db&#34;&gt;DBA Tasks in Azure DB&lt;/h2&gt;&#xA;&lt;p&gt;It was a big surprise to me when I learned that Azure SQL Database doesn&amp;rsquo;t update statistics or indexes automatically. The option to automatically update statistics exists (e.g., ALTER DATABASE [WideWorldImporters] SET AUTO_UPDATE_STATISTICS ON), and is on by default, but it does not give the same control as updating them manually with the &amp;lsquo;UPDATE STATISTICS&amp;rsquo; command. When Azure DB was first pitched to us, on an internal project, one of the big selling points was &amp;ldquo;no maintenance required&amp;rdquo;. This wasn&amp;rsquo;t a statement from Microsoft or even from the documentation. It was clearly a marketing talking-point that leaked into the technical discussions. It&amp;rsquo;s partially true. Some things are automatic, but there are a few things you still need to maintain or at least monitor yourself. The big shocker, as you already know from the first sentence above, is that indexes aren&amp;rsquo;t automatically rebuilt for you and statistics aren&amp;rsquo;t maintained beyond the database configuration item.&lt;/p&gt;</description>
			</item>
	</channel>
</rss>
