<?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: vCenter Database Stats Rollup Troubleshooting</title>
	<atom:link href="http://vmtoday.com/2009/09/vcenter-database-stats-rollup-troubleshooting/feed/" rel="self" type="application/rss+xml" />
	<link>http://vmtoday.com/2009/09/vcenter-database-stats-rollup-troubleshooting/</link>
	<description>VMware News, Views, &#38; How-To&#039;s from Josh Townsend</description>
	<lastBuildDate>Mon, 22 Feb 2010 19:38:06 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Richard</title>
		<link>http://vmtoday.com/2009/09/vcenter-database-stats-rollup-troubleshooting/comment-page-1/#comment-178</link>
		<dc:creator>Richard</dc:creator>
		<pubDate>Sun, 25 Oct 2009 20:32:42 +0000</pubDate>
		<guid isPermaLink="false">http://vmtoday.com/?p=240#comment-178</guid>
		<description>Thanks for the write up, I found it extremely helpful.  However, I found a discrepancy in what happened on my vCenter 2.5 migration.  Perhaps there were changes between 2.5 and 4.0.

In your write-up you talk about the stored procedures not being transfered after a vCenter server migration.  What I found on ours was that all the stored procedures were there, both the roll up and purge procedures, but it was the scheduled tasks in the SQL Server Agent that didn&#039;t move.

For your remediation to add these back you say to use the stats_rollup*_proc_mssql.sql scripts, but these add the roll up stored procedures.  The scripts to install the SQL Server Agent jobs are actually the job_schedule*_proc_mssql.sql scripts.

Again, thanks for the article.</description>
		<content:encoded><![CDATA[<p>Thanks for the write up, I found it extremely helpful.  However, I found a discrepancy in what happened on my vCenter 2.5 migration.  Perhaps there were changes between 2.5 and 4.0.</p>
<p>In your write-up you talk about the stored procedures not being transfered after a vCenter server migration.  What I found on ours was that all the stored procedures were there, both the roll up and purge procedures, but it was the scheduled tasks in the SQL Server Agent that didn&#8217;t move.</p>
<p>For your remediation to add these back you say to use the stats_rollup*_proc_mssql.sql scripts, but these add the roll up stored procedures.  The scripts to install the SQL Server Agent jobs are actually the job_schedule*_proc_mssql.sql scripts.</p>
<p>Again, thanks for the article.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mancil</title>
		<link>http://vmtoday.com/2009/09/vcenter-database-stats-rollup-troubleshooting/comment-page-1/#comment-126</link>
		<dc:creator>Mancil</dc:creator>
		<pubDate>Thu, 24 Sep 2009 14:57:17 +0000</pubDate>
		<guid isPermaLink="false">http://vmtoday.com/?p=240#comment-126</guid>
		<description>Thanks for this write up - found it very helpful in solving our problems</description>
		<content:encoded><![CDATA[<p>Thanks for this write up &#8211; found it very helpful in solving our problems</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: matt</title>
		<link>http://vmtoday.com/2009/09/vcenter-database-stats-rollup-troubleshooting/comment-page-1/#comment-113</link>
		<dc:creator>matt</dc:creator>
		<pubDate>Tue, 22 Sep 2009 12:51:47 +0000</pubDate>
		<guid isPermaLink="false">http://vmtoday.com/?p=240#comment-113</guid>
		<description>it&#039;s called RRDtool, vmware! why am I not surprised vmware programmers are so stupid as to put metrics in a sql database where they never belong.</description>
		<content:encoded><![CDATA[<p>it&#8217;s called RRDtool, vmware! why am I not surprised vmware programmers are so stupid as to put metrics in a sql database where they never belong.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
