Sign In with your
Trend Micro Account
Need Help?
Need More Help?

Create a technical support case if you need further support.

Determining the Control Manager (TMCM) table that has the most number of records

    • Updated:
    • 21 Oct 2015
    • Product/Version:
    • Control Manager 6.0
    • Platform:
    • Windows 2003 Enterprise
    • Windows 2008 Enterprise
    • Windows 2008 Enterprise 64-bit
    • Windows 2008 Server R2
Summary

Learn how to determine which TMCM table has the most number of records.

The TMCM database is the backbone of the product's operation, management, and reporting feature. It has a function that maintains the database (DB) size, but there are times when a table (or several tables) grows too big in size because of the automatic log purging task that needs to be completed. This makes the product unstable or fills up the SQL transaction log and causes disk space problems.

Details
Public

There are two ways to determine which table has the most number of records in TMCM database:

Option 1: Using an SQL script

  1. Run the following SQL script from the Microsoft SQL Server Management Studio:

    select 'Owner'=convert(char(10),t.TABLE_SCHEMA), 'Table Name'=convert(char(25),t.TABLE_NAME), 'Record Count'=max(i.rows) from sysindexes i, INFORMATION_SCHEMA.TABLES t where t.TABLE_NAME = object_name(i.id) and t.TABLE_TYPE = 'BASE TABLE' group by t.TABLE_SCHEMA, t.TABLE_NAME order by [Record Count] desc;

  2. Save the .CSV file.

Option 2: Using the Microsoft SQL Server Management Studio

  1. Open Microsoft SQL Server Management Studio and right-click the TMCM database.

    By default, the TMCM database name is db_controlmanager.

  2. Click Reports > Standard Reports.
  3. Generate a report for each of the following:
    • Disk Usage
    • Disk Usage by Top Tables
    • Disk Usage by Table

Trend Micro recommends that you send the .CSV file and/or the report files to Trend Micro Technical Support to determine if the table can be truncated or not. A table that is incorrectly truncated can cause you to lose important logs that are needed for reporting and may also cause the product to malfunction in terms of console access and stability.

Premium
Internal
Rating:
Category:
Troubleshoot
Solution Id:
1060954
Feedback
Did this article help you?

Thank you for your feedback!

To help us improve the quality of this article, please leave your email here so we can clarify further your feedback, if neccessary:
We will not send you spam or share your email address.

*This form is automated system. General questions, technical, sales, and product-related issues submitted through this form will not be answered.

If you need additional help, you may try to contact the support team. Contact Support


To help us improve the quality of this article, please leave your email here so we can clarify further your feedback, if neccessary:
We will not send you spam or share your email address.

*This form is automated system. General questions, technical, sales, and product-related issues submitted through this form will not be answered.


Need More Help?

Create a technical support case if you need further support.