Go to documentation repository
Documentation for Intellect 4.11.0-4.11.3. Documentation for other versions of Intellect is available too.
To complete the following steps, it is required that SQL Server Management Studio is installed on the server.
If this type of SQL error occurs, it means that the database has grown too large. Usually it happens when a large number of events are written to the PROTOCOL table.
To fix this problem, do the following:
- Clear the PROTOCOL table partially or completely:
- If the PROTOCOL table contains important events that should not be removed, or if the Report System is used, then you should manually remove some events from the event database. Do it as follows:
- Determine which events can be removed from the database.
Remove these events using SQL queries.
Complete guide: Removing the events from the PROTOCOL table using SQL queries
- After that, go to step 4, and then sequentially complete steps 2 and 3.
If the PROTOCOL table does not contain important events, and the Report System is not used, then manually delete the PROTOCOL table for the server with error.
Complete guide: Removing the event table from the Intellect database
- If the PROTOCOL table contains important events that should not be removed, or if the Report System is used, then you should manually remove some events from the event database. Do it as follows:
Compress the database.
Complete guide: Compressing the database size
Set the minimum parameters for storing log files for the database. You can do it either on the settings panel of the Intellect section in the tweaki.exe utility, or by using the registry keys.
Complete guide: Enabling and configuring the debug mode of Intellect software
Set a time limit for storing events in Intellect.
Complete guide: Configuring events logging
You can also disable event logging using the ddi.exe utility. Disabled events can be deleted, which also helps clean up the database. For this, use SQL queries.
Complete guide: The Events tab