Posted by ZeldorBlat on 05/02/07 17:02

On May 2, 11:41 am, "Ben" <nos...@thankyou.com> wrote:
> 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

Common database design principles tell us that the schema should
remain (relatively) unchanged throughout the life of the application.
i.e. You don't add a new table when you add a new customer to your
system (or, in this case, a new day). So the first answer is the
correct one.

[Back to original message]