<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Controlling Growth of a msdb Database</title>
	<atom:link href="http://www.sql-server-performance.com/2011/controlling-growth-msdb-database/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.sql-server-performance.com/2011/controlling-growth-msdb-database/</link>
	<description>SQL Server Performance Tuning</description>
	<lastBuildDate>Fri, 17 May 2013 13:31:24 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.5.1</generator>
	<item>
		<title>By: satnam singh</title>
		<link>http://www.sql-server-performance.com/2011/controlling-growth-msdb-database/#comment-2369</link>
		<dc:creator>satnam singh</dc:creator>
		<pubDate>Wed, 07 Nov 2012 07:30:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.sql-server-performance.com/?p=2773#comment-2369</guid>
		<description><![CDATA[See if you can shrink the physical files of the database, 4 GB for msdb database seems to be pretty fair.]]></description>
		<content:encoded><![CDATA[<p>See if you can shrink the physical files of the database, 4 GB for msdb database seems to be pretty fair.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dinesh</title>
		<link>http://www.sql-server-performance.com/2011/controlling-growth-msdb-database/#comment-2368</link>
		<dc:creator>Dinesh</dc:creator>
		<pubDate>Wed, 07 Nov 2012 06:48:10 +0000</pubDate>
		<guid isPermaLink="false">http://www.sql-server-performance.com/?p=2773#comment-2368</guid>
		<description><![CDATA[Hi,
All object shows data values space is zero.
but msdb stil having 4967mb space.
what will cause ??]]></description>
		<content:encoded><![CDATA[<p>Hi,<br />
All object shows data values space is zero.<br />
but msdb stil having 4967mb space.<br />
what will cause ??</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: deepali</title>
		<link>http://www.sql-server-performance.com/2011/controlling-growth-msdb-database/#comment-1274</link>
		<dc:creator>deepali</dc:creator>
		<pubDate>Mon, 30 Jan 2012 06:26:05 +0000</pubDate>
		<guid isPermaLink="false">http://www.sql-server-performance.com/?p=2773#comment-1274</guid>
		<description><![CDATA[good article]]></description>
		<content:encoded><![CDATA[<p>good article</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Wilfred van Dijk</title>
		<link>http://www.sql-server-performance.com/2011/controlling-growth-msdb-database/#comment-1265</link>
		<dc:creator>Wilfred van Dijk</dc:creator>
		<pubDate>Wed, 25 Jan 2012 07:53:06 +0000</pubDate>
		<guid isPermaLink="false">http://www.sql-server-performance.com/?p=2773#comment-1265</guid>
		<description><![CDATA[Pesonally, I found the title a little misleading. What you describe should be a part of regular database maintenance. In my opinion, controlling the size of MSDB should be about purging data on a regular basis. Have a look at procedures like sp_purge_jobhistory or procedures which starts with &#039;sp_delete_%&#039;. In case of logshipping there are some routines to keep the size of these in control.
In case of maintaining databases: there are a lot of scripts to do this. I recommend the solution from http://ola.hallengren.com/]]></description>
		<content:encoded><![CDATA[<p>Pesonally, I found the title a little misleading. What you describe should be a part of regular database maintenance. In my opinion, controlling the size of MSDB should be about purging data on a regular basis. Have a look at procedures like sp_purge_jobhistory or procedures which starts with &#8216;sp_delete_%&#8217;. In case of logshipping there are some routines to keep the size of these in control.</p>
<p>In case of maintaining databases: there are a lot of scripts to do this. I recommend the solution from <a href="http://ola.hallengren.com/" rel="nofollow">http://ola.hallengren.com/</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Marco</title>
		<link>http://www.sql-server-performance.com/2011/controlling-growth-msdb-database/#comment-1264</link>
		<dc:creator>Marco</dc:creator>
		<pubDate>Wed, 25 Jan 2012 06:46:10 +0000</pubDate>
		<guid isPermaLink="false">http://www.sql-server-performance.com/?p=2773#comment-1264</guid>
		<description><![CDATA[Uhm, I hope you&#039;re not running the update-statistics (which computes an approximation of the stats) right after the index-rebuild (which by itself obtains accurate statistics on the newly created index).
In other words, doing an update-statistics right after an index-rebuild is pointless or even detrimental on large tables since the update-statistics takes a less accurate approach (=record-samples instead of looking at each indexed record) in favor of performance]]></description>
		<content:encoded><![CDATA[<p>Uhm, I hope you&#8217;re not running the update-statistics (which computes an approximation of the stats) right after the index-rebuild (which by itself obtains accurate statistics on the newly created index).<br />
In other words, doing an update-statistics right after an index-rebuild is pointless or even detrimental on large tables since the update-statistics takes a less accurate approach (=record-samples instead of looking at each indexed record) in favor of performance</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Idris Chambas</title>
		<link>http://www.sql-server-performance.com/2011/controlling-growth-msdb-database/#comment-1242</link>
		<dc:creator>Idris Chambas</dc:creator>
		<pubDate>Wed, 18 Jan 2012 19:27:36 +0000</pubDate>
		<guid isPermaLink="false">http://www.sql-server-performance.com/?p=2773#comment-1242</guid>
		<description><![CDATA[Very useful tip.
Thanks]]></description>
		<content:encoded><![CDATA[<p>Very useful tip.<br />
Thanks</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Diane</title>
		<link>http://www.sql-server-performance.com/2011/controlling-growth-msdb-database/#comment-1102</link>
		<dc:creator>Diane</dc:creator>
		<pubDate>Thu, 22 Dec 2011 22:46:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.sql-server-performance.com/?p=2773#comment-1102</guid>
		<description><![CDATA[You pointed roughly finicky subject matter. These tips are very beneficial.
&lt;a href=&quot;http://acnetreatments250.blinkweb.com/&quot; / rel=&quot;nofollow&quot;&gt;Acne medication&lt;/a&gt;]]></description>
		<content:encoded><![CDATA[<p>You pointed roughly finicky subject matter. These tips are very beneficial.<br />
<a href="http://acnetreatments250.blinkweb.com/" / rel="nofollow">Acne medication</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ravi Agarwal</title>
		<link>http://www.sql-server-performance.com/2011/controlling-growth-msdb-database/#comment-1076</link>
		<dc:creator>Ravi Agarwal</dc:creator>
		<pubDate>Wed, 21 Dec 2011 12:00:35 +0000</pubDate>
		<guid isPermaLink="false">http://www.sql-server-performance.com/?p=2773#comment-1076</guid>
		<description><![CDATA[Good Article........]]></description>
		<content:encoded><![CDATA[<p>Good Article&#8230;&#8230;..</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Sejal</title>
		<link>http://www.sql-server-performance.com/2011/controlling-growth-msdb-database/#comment-1074</link>
		<dc:creator>Sejal</dc:creator>
		<pubDate>Wed, 21 Dec 2011 09:53:20 +0000</pubDate>
		<guid isPermaLink="false">http://www.sql-server-performance.com/?p=2773#comment-1074</guid>
		<description><![CDATA[Good Article....]]></description>
		<content:encoded><![CDATA[<p>Good Article&#8230;.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
