Comments on: vCenter Database Stats Rollup Troubleshooting

By: Ahmed

Ahmed — Wed, 28 Sep 2011 03:49:32 +0000

I’m writing here as after hours of troubleshooting this post fixed everything for me. A couple things to note:

The procedures may still be existing, as such you’ll need to remove them:

http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1009857

Additionally, the queries you mention in your post will not recreate the jobs, take a look at this KB:

http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1004382

By: Richard

Richard — Sun, 25 Oct 2009 20:32:42 +0000

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’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.

By: Mancil

Mancil — Thu, 24 Sep 2009 14:57:17 +0000

Thanks for this write up – found it very helpful in solving our problems

By: matt

matt — Tue, 22 Sep 2009 12:51:47 +0000

it’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.