Jdog,
In response to para 3 of your posting, here is the link to the documentation PDF:
http://support.businessobjects.com/documentation/product_guides/download.asp?manual=boexir2/en/xir2_bip_auditor_en.pdf
Also, look at page 36, it is the Entity-Relationship Diagram (ERD) for the Auditor database which will help you to better understand the database schema.
The two objects you mentioned:
are both part of the “transaction” portion of the schema, i.e., these tables (and data points) grow with each influx of auditor data, but not to discourage you from building an index on this stuff, but just be aware of the “growth” factor…
If you’re open to a more philosophical discussion, how about thinking to trim down your auditor database? If you have ~22 million rows and its choking a horse, why live with that? If you think that the auditor data is valuable, I would suggest creating another database area, replicate your ~22 million rows over to it, then delete all of the 2008 data from the new area, and delete all of the non-2008 data back in the original area. Now you’ll have two databases (historical – pre-2008) and current (2008 only). Then you could possibly build (replicate) the Auditor universe pointing at the old data for “historical auditor info”, and get back to the good life. Just a thought in wrapping your arms around this bear.
Thanks,
John
P.S. the “formula” for properly mass deleting data from auditor (in XI R2) is back over in the Auditor forum (see here)https://bobj-board.org/t/105734
jsanzone 
(BOB member since 2006-09-12)