FYI here's the results of the row counts:
Code: +-----------------------------+---------+----------+ | device | count | severity | +-----------------------------+---------+----------+ (snip) | pw02welcome | 62457 | 5 | | virtual6 | 65012 | 5 | | virtual4 | 70667 | 5 | | virtual3 | 84971 | 5 | | virtual5 | 89728 | 5 | | accessct-server | 91027 | 5 | | vm | 106512 | 5 | | outside | 107719 | 5 | | sqlserver | 118548 | 5 | | virtual2 | 131536 | 5 | | fileserver | 770885 | 5 | | virtual1 | 3231723 | 5 | | server04 | 3325877 | 5 | | server05 | 3936322 | 5 | +-----------------------------+---------+----------+ 46 rows in set (1 hour 21 min 5.83 sec) It looks like my domain controllers and print server are pretty noisy. 3-4 million rows for each in only a few weeks. I suppose when you multiple each row times the length of the characters for each "event" that probably explains the large size of the database. At least I know where to start pruning now. Thanks for your assistance, I believe this will be very useful. -------------------- m2f -------------------- Read this topic online here: http://community.zenoss.com/forums/viewtopic.php?p=12986#12986 -------------------- m2f -------------------- _______________________________________________ zenoss-users mailing list [email protected] http://lists.zenoss.org/mailman/listinfo/zenoss-users
