SE and big databases or RAID

I know this is will generate remarks like "Use Online, stupid!", but... I have a customer running SE for the obvious cost savings over Online. We are projecting a database size in the 2 to 4 million rows size for one of the big tables. The records are not large, 15 rows for a total of 126 bytes. The database will probably take over a year to get there, but it is expected to get that big. Has anybody ever run SE that large? I expect to see some performance degradation, but the customer is prepared to throw more money at the hardware before he will hire someone to maintain Online. The customer already has 250,000 records and is very pleased with current performance. Also, he plans on placing the SE dbs on a RAID system. Anybody ever done this? I can't think of a reason to hae a problem, but hey, anything is possible. -=-=-=-=-=-=-=-=-=-=-=-=- Informix Premier Var -=-=-=-=-=-=-=-=-=-=-=-=-=-=- Miguel A. Caldera Antares Development Corp. Phone (210) 490-9626 Dir, Prod Development 1000 Central Pkwy North Fax (210) 490-0874 mac@antares-dev.com San Antonio, TX 78232 USA #include <std_disclaim.h> -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- =-> You can teach 'em code, but you can't teach 'em logic! <-=