My history logs have grown beyond capacity of my sql database and need to remove a lot of the entries in the logs....Help!

I'm having a problem with my cbsubs history logs. I do my hosting with go-daddy and was informed that my sql database had grown beyond the 1GB limit. I thought there is no way my database could have gown so large in such a short period of time.
Upon taking a closer look all the tables except the jos_cbsubs_history history table which has grown to some 3.5GB in size. I need to get this back under the 1MB limit fast before I can look at what this error is. Can someone either show me a way to dump thousands of records of this error from the error or history log? I've tried using your cb_subs query tool in the history logs but I cannot do more than a couple hundred at a time and have some 196,000+ records I need to remove quickly ore have my database inactivated for exceeding the maximum size. Not sure how to properly do this without it effecting the subscriptions software. Could someone please help with this matter or give me some help constructing the correct delete query to remove these records? I have a pretty good working knowledge of MySQL but don't want to make matter worst. Any help would be greatly appreciated. I've got 3 days to bring this under control. Thanks in advance for taking the time to help.
bucknla.

It's perfectly fine to empty the entire _cbsubs_history table within your database. The history log is not vital to CBSubs functioning in any way. However, it's going to keep filling up because you are ignoring notices, warnings, or errors; you should review the log entry and see if the issue can be resolved. Note unresolved notices, warnings, and errors do cause performance loss so it's always best to try and fix them.

This happens to me a lot. I'm using: TRUNCATE TABLE yourTableName_cbsubs_history;

Regards
Ricco

You may want to contact your host and see if a CRON job can be setup to run database queries regularly to clear it. We've plans to implement a CRON endpoint to handle history clean up in a later CBSubs release.

We've plans to implement a CRON endpoint to handle history clean up in a later CBSubs release

Is this an option yet?

No, it has not been implemented yet, but you can do this with CB Auto Actions. Create a new auto action as follows.

Global
Triggers: None
Type: Query
User: Automatic
Access: Everybody
Action
Query:
Then just schedule CRON to run the direct action URL under the global tab as needed. That's more or less all that the CRON endpoint in CBSubs would be doing. Could get more specific as well if you only want to delete certain history rows, etc..