|
Problem |
SE_TABLE keeps growing and consuming more disk space. |
|
Cause |
The Log limit is set too high, creating a very large
SE_TABLE. |
|
Solution |
SE_TABLE is a logging and history table. Maximum rows in this table are
controlled using the Log limit value in Event Viewer
Properties. The Log limit property in the Event Viewer Options window
refers to how many server event records (audit messages, warning messages,
severe errors) you want to keep in the administrative repository database
in the SE_TABLE.
When the log limit is reached and a new serious event occurs, the record
for the oldest event is discarded and a record is created for the new
event.
 |
|
|
|
|
|
|