<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://blogs.msdn.com/utility/FeedStylesheets/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>SQL Server Best Practices: Auto-Shrink Should Be Off</title><link>http://blogs.msdn.com/buckwoody/archive/2009/07/01/sql-server-best-practices-auto-shrink-should-be-off.aspx</link><description>SQL Server is one of the easiest databases to maintain because of all of the automatic settings it has, but as I mentioned with Auto-Close, some of them should be left off. The Auto-Shrink setting is another. That might surprise a few people. You might</description><dc:language>en-US</dc:language><generator>CommunityServer 2.1 SP1 (Build: 61025.2)</generator><item><title>re: SQL Server Best Practices: Auto-Shrink Should Be Off</title><link>http://blogs.msdn.com/buckwoody/archive/2009/07/01/sql-server-best-practices-auto-shrink-should-be-off.aspx#9856324</link><pubDate>Mon, 03 Aug 2009 18:50:35 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:9856324</guid><dc:creator>hfrmobile</dc:creator><description>&lt;p&gt;&amp;quot;I never shrink my databases unless I have a huge deletion of data, and I know that the data won't come back.&amp;quot;&lt;/p&gt;
&lt;p&gt;--&amp;gt; I agree ;-) In my current project we have such a situation one time / year.&lt;/p&gt;
</description></item></channel></rss>