<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Sys.dm_exec_input_buffer on SQL Server Scripts</title><link>https://www.sqlserver70.com/tags/sys.dm_exec_input_buffer/</link><description>Recent content in Sys.dm_exec_input_buffer on SQL Server Scripts</description><generator>Hugo -- gohugo.io</generator><language>en</language><copyright>SQLServer70.com</copyright><lastBuildDate>Mon, 08 Jun 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://www.sqlserver70.com/tags/sys.dm_exec_input_buffer/index.xml" rel="self" type="application/rss+xml"/><item><title>SQL Server DBCC Commands: The Complete DBA Reference Guide</title><link>https://www.sqlserver70.com/post/sql-server-dbcc-commands-reference/</link><pubDate>Mon, 08 Jun 2026 00:00:00 +0000</pubDate><guid>https://www.sqlserver70.com/post/sql-server-dbcc-commands-reference/</guid><description>
&lt;p&gt;An incident rarely announces which DBCC statement it needs. A log file stops truncating, a query slows after a plan changes, an identity column runs ahead of its table, and each one has a Database Console Command that answers it, sitting next to a few that can make the same situation worse. The DBCC statements are easiest to handle sorted by what they are used for, with a runnable statement for the ones you reach for most and a note on each one's cost and permissions.&lt;/p&gt;</description></item></channel></rss>