HQEventLog table size and maintainance

I am Running RMS HQ with 38 stores and growing. Each store has two POS lanes and we don't do a large volume of transactions in any given day. The size of my DB is concerning me, so I ran a query that returns the size of each table, and what I found is that 95% of the size of my HQ DB is contained in "HQEventLog" and "TimeStandLog". What I want to know is 1. Would there be any long term problem in periodically purging anything in either/both of these tables that is older than 30 days? 2. What would be the best way to do this (script to use and any suggestions for automation would be great). Just to give you an idea, the current size of the HQEventLog table reports at

Thanks, Brandon