>When I get a response for some EDI stuff, there is a summary table, one record per request/response, and a detail table that could contain anywhere from 100 to 800 records for each summary record. I don't think there is much I can do at this point about the number of detail records per summary record, but is there anything I can do to make sure this doesn't blow up or slow down significantly as it grows? I will be flagging the summary records as Archive once they have been reviewed and if they are also older than a set time (currently 7 days). But I'm not sure what to do with them, if anything, as there is an option to include the Archive records in the UI and for reporting. So, they need to be handy. Over time I could see this becoming millions of detailed records if left as is. Any thoughts?

I suggest that you store the detail EDI documents as separate files, and only store the filenames in your table.