The GroomHistory Table in MOM 2000 May Become Very Large (314219)
The information in this article applies to:
- Microsoft Operations Manager 2000
This article was previously published under Q314219 SYMPTOMS
Microsoft Operations Manager (MOM) 2000 tracks groomed data operations in the GroomHistory table in the OnePoint database in Microsoft SQL Server. Over time, the GroomHistory table may become very large.
CAUSE
The rows in the GroomHistory table are never deleted by MOM. This can cause the table to become very large if you groom data frequently in MOM.
WORKAROUND
You can manually delete rows from the GroomHistory table to reclaim database space. Use the following Transact-SQL statement in SQL Query Analyzer to delete a range of rows from the table. Microsoft recommends that you back up the table before you run any queries against the table.
USE OnePoint
DELETE FROM GroomHistory
WHERE TimeEnded < 'May 1, 1997'
Change the date in the query to an appropriate date for your database, based on activity that should be retained as defined by your organizational needs.
STATUSMicrosoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article. MORE INFORMATION
For more information about using Transact-SQL queries, refer to the SQL Server online documentation.
| Modification Type: | Minor | Last Reviewed: | 6/13/2005 |
|---|
| Keywords: | kbenv kbprb KB314219 |
|---|
|