A customer installed a new instance of Operations Manager 2007 R2 CU 4 and added some management packs for monitoring server, sql, active directory and exchange.
Also the agent was deployed to 10 servers in the infrastucture to tune the managment packs.
After round about one week, the OperationsManager database size was 4GB.
Five days later, it was at nearly 8GB big.
So the customer asked, if that growing is as expected and was surprised, that we told him, it should be quite below 1GB with this amount of management packs and agents.
To get a handle on the fast growing of the database site, I stumbled over a create blog from Kevin Holeman about “Useful Operations Manager 2007 SQL queries”.
Yes, it is an old article, but it is the best for finding spammers that fill up the database by running some queries against it.
In conclusion:
The unexpected database growing was caused by the event collection rule from the exchange management pack and a leftover form exchange troubleshooting that traced verbose into the eventlog on a mailbox server.
Thanks Kevin for an other very usefull blog post.
COMMENTS