Reasonable Table Size

We are creating a new application using 2 Gig of data per week with 2 years on line (approx 104 gig total). This is all "logically" a single table. Does anyone have a feel for what a reasonable size is for large tables? Can this be created as a single table, or should it be broken into smaller tables (if so, what size) and joined via a view? My fear is that the maintenance on such a large table would be costly and would make exporting/importing if needed impossible. Also expensive would be loading the data each week and rebuilding the entire index.

Any comments would be appreciated.

Ron Lammardo
NYS Department of Social Services
Albany,NY Received on Thu Apr 03 1997 - 00:00:00 CST