200 to 300 Gigabytes Database

Fellow netters, Have any of you out there ever had to deal with a very LARGE database like 200 to possibly 300 gigabytes? I have a client here that will require a database that can hold 1 to 1.5 gigabytes of data every day and he requires at least 200 days of history in the database. The database will be an INFORMIX 5.0 engine and the application will be written in INFORMIX 4GL 4.1. The database will be mainly for queries and only very few updates will be done. My colleague and I have tried to come up with some way to break this database into more manageable sizes. We thought about breaking down this database into multiple databases, like having a separate database to store each day of data. We also talked about having multiple instances of Online combined with multiple databases in each instance. Our main goals are: 1) to minimize downtime 2) to improve efficiency in data access. Any comments, ideas or suggestions would be very appreciated. ---- Regards, Francis Chue Unix System Project Leader American TriTech Internet: fsc0@isg.com 10717 Sorrento Valley Road Voice : (619)453-7000 ext. 283 San Diego, CA 92121 Fax : (619)453-8709