Posted by Ben on 05/02/07 15:41

This is a theoretical design question as to how to address an issue where a
certain table with ~20 fields will grow rapidly (20,000 records per day) and
we need to keep all records in the active DB for seven years. We're talking
about > 50 million records.

I see two approaches to this:

1.) Single table using raid

2.) One table per day (365x7 = 2555 tables) and build an object to
interface as if it were a single table.

Which (if any) approach would you think is better where better = fast
response time and overall maintenance.

TYIA

=B

[Back to original message]