<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>DBCC SHRINKFILE on SQL Server Scripts</title><link>https://www.sqlserver70.com/tags/dbcc-shrinkfile/</link><description>Recent content in DBCC SHRINKFILE 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/dbcc-shrinkfile/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;Every SQL Server instance ships with a parallel command vocabulary that never appears in an ORM, a stored procedure, or an application query: the DBCC statements. They validate physical page structure, reclaim file space, evict cached plans, reseed identity columns, and report internal counters that no &lt;code&gt;SELECT&lt;/code&gt; exposes — and a DBA who does not know which one to reach for in an incident reaches for the wrong one. This guide maps the DBCC surface area by family, shows a representative statement for each, and links to deep dives on the commands you run most.&lt;/p&gt;</description></item><item><title>SQL Server DBCC SHRINKDATABASE: When and When Not to Shrink</title><link>https://www.sqlserver70.com/post/sql-server-dbcc-shrinkdatabase-when-to-shrink/</link><pubDate>Fri, 05 Jun 2026 00:00:00 +0000</pubDate><guid>https://www.sqlserver70.com/post/sql-server-dbcc-shrinkdatabase-when-to-shrink/</guid><description>
&lt;p&gt;A one-time data load doubled a data file overnight, the load is done, the rows are deleted, and the file is now mostly empty space. The reflex — reach for &lt;code&gt;DBCC SHRINKDATABASE&lt;/code&gt; and give the disk back — is one of the most common self-inflicted performance wounds in SQL Server administration. This post explains exactly what shrinking does to your indexes, when it is genuinely the right call, and how to reclaim space the few times you must without wrecking performance.&lt;/p&gt;</description></item></channel></rss>