Re: Informix handling VLDBs

One thing you can do is creat your own cache table. If a row is going to be repeated used in near future, keep a copy of this records in the much smaller cache table. If you need to retrieve it, you can pick it up from the smaller table. But, when you update the row, you must update both big and small table. If you have new data come in, and you expect to do a weekly statistics on those new data. You could keep an extra copy of the new data in a small table. You can clean out the new-data-small-table by using a cron job. Build index on big table, of course. Regards! William Zhu __ -----------------------------\\/--------------bzhu@copley.com----------- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~<__>~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ On 18 Jan 1995, SLIP User wrote: > I am interested in any experiences of the use of Informix in Very Large > Database projects. I am currently involved in a project which will need > to hold in excess of 100million rows of data. This data will need to be > accessed and retrieved as if it were all in one table, that is, we will > need to select a record from this data based upon phone number, unique > id, user name, address etc. > > Anyway, I am in search of experience in the use of VLDBs in Informix, or > any other platforms for that matter. Any help would be greatly helpful. > Since we are still in the evaluation stage, any contacts with relevant > experience would be appreciated. I need to know how the rest of the > world has delt with similar problems... Thanks in advance. > > -- > Timothy R Myers | "More people would learn from their > Lancaster, PA USA | mistakes if they weren't so busy > tmyers@eipx.net | denying them." >