We have a customer who has a relatively small repository.  Only 17,000 documents/850,000 images.  We noticed that their SQL database has grown to over 260 GB, with a 15 GB log file.

I ran a sql statement which shows me the number of rows, and associated size of each table in the database, and found something interesting.  There are 4 tables which appear to be taking up most of the space.  They are:

journal_entry:  504,419,956 rows, 130 GB total space
bizproc_entity:  252,210,364 rows, 58 GB total space
journal:  126,105,028 total rows, 8 GB total space
bizproc_entity_entry:  126,105,175 rows, 6 GB total space

Can anybody tell me what these tables are used for?  I checked our own internal DB, and the Journal_entry table has zero rows.  I'm not sure what is causing this table to grow out of control in this way.  Is it related to Workflow somehow?  They don't have many workflows, but I did just notice that they had one workflow running in an endless loop (A workflow which made a change to a document, had a starting condition which was looking for Entry Change, and was not excluding the Workflow user, so as soon as the workflow finished processing, it would kick off again).

Any help would be appreciated!