https://www.sqlserver70.com/tags/xp_cmdshell/Recent content in Xp_cmdshell on SQL Server ScriptsHugo -- gohugo.ioenSQLServer70.comMon, 24 Aug 2026 00:00:00 +0000https://www.sqlserver70.com/post/server-configuration-drift-sys-configurations/Mon, 24 Aug 2026 00:00:00 +0000https://www.sqlserver70.com/post/server-configuration-drift-sys-configurations/ <p>Running <code>sp_configure</code> and getting back a success message is not the same thing as a setting actually taking effect. Between the moment a value is changed and the moment <a href="https://learn.microsoft.com/en-us/sql/sql-server/">SQL Server</a> is actually running it sits a gap — one a busy DBA can close with a single <code>RECONFIGURE</code>, or forget entirely until a restart months later flips a setting no one meant to touch yet. <a href="https://learn.microsoft.com/en-us/sql/relational-databases/system-catalog-views/sys-configurations-transact-sql">sys.configurations</a> is where that gap is visible: its <code>value</code> and <code>value_in_use</code> columns don't have to match, and when they don't, this script says exactly why not and what to do about it.</p>