<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Database Configuration on SQL Server Scripts</title><link>https://www.sqlserver70.com/tags/database-configuration/</link><description>Recent content in Database Configuration on SQL Server Scripts</description><generator>Hugo -- gohugo.io</generator><language>en</language><copyright>SQLServer70.com</copyright><lastBuildDate>Tue, 27 Oct 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://www.sqlserver70.com/tags/database-configuration/index.xml" rel="self" type="application/rss+xml"/><item><title>Audit Per-Database MAXDOP, CE and Sniffing Config Overrides</title><link>https://www.sqlserver70.com/post/audit-per-database-maxdop-ce-and-sniffing-config-overrides/</link><pubDate>Tue, 27 Oct 2026 00:00:00 +0000</pubDate><guid>https://www.sqlserver70.com/post/audit-per-database-maxdop-ce-and-sniffing-config-overrides/</guid><description>
&lt;p&gt;A database &lt;a href="https://learn.microsoft.com/en-us/sql/relational-databases/system-catalog-views/sys-database-scoped-configurations-transact-sql?view=sql-server-ver17"&gt;restored from another server&lt;/a&gt;, or built by a vendor's install script, can carry its own MAXDOP, cardinality estimation model or parameter sniffing setting, and that setting &lt;a href="https://learn.microsoft.com/en-us/sql/t-sql/statements/alter-database-scoped-configuration-transact-sql?view=sql-server-ver17"&gt;overrides the server-wide default&lt;/a&gt;. The query below lists every database scoped option in the current database, &lt;a href="https://learn.microsoft.com/en-us/sql/relational-databases/system-catalog-views/sys-database-scoped-configurations-transact-sql?view=sql-server-ver17"&gt;one row per configuration&lt;/a&gt;, with the value the primary uses next to the value its secondaries use. Run it once in each database you are checking.&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;One database starts producing serial plans, or plans built on the old cardinality estimator. Every other database on the instance behaves, and the server-level &lt;code&gt;max degree of parallelism&lt;/code&gt; is where it should be. The cause sits one level down. Database scoped options show up only in &lt;code&gt;sys.database_scoped_configurations&lt;/code&gt;, as &lt;a href="https://learn.microsoft.com/en-us/sql/t-sql/statements/alter-database-scoped-configuration-transact-sql?view=sql-server-ver17"&gt;overrides to server-wide default settings&lt;/a&gt;, and &lt;code&gt;sys.configurations&lt;/code&gt; shows server-wide settings only.&lt;/p&gt;</description></item></channel></rss>