John W. Colby
jwcolby at colbyconsulting.com
Wed Sep 1 19:18:23 CDT 2004
And for the record, by the time I index this database it will be well over a terabyte. If I end up merging in their other databases it will be several terabytes. John W. Colby www.ColbyConsulting.com -----Original Message----- From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Francisco Tapia Sent: Tuesday, August 31, 2004 8:02 PM To: Access Developers discussion and problem solving Subject: Re: [AccessD] Every 100th record For the record I think it was me who applied the term VLDB to his db :D. Even thow I've been my dept's DBA for the last 3 years, I have not run into any company database that touches the Millions of records, the only tables that I have that contain a near enough number of consequential tables, (auditing) On Tue, 31 Aug 2004 19:32:55 -0400, Arthur Fuller <artful at rogers.com> wrote: > Just to put things in perspective, JC, the first client of the people > who developed MySQL had 60M rows in their principal table. There are > lots of apps way bigger than that. I once had a client that was adding > 10M rows per month to the table of concern (this was an app recording > seismic activity from several hundred meters). I must caution you that > you should not use the term VLDB as loosely as you have been using it. > You don't know the meaning of VLDB -- not yet at least. You're > beginning to appreciate the turf, however. Once I bid on a project > that had 100M rows each containing a graphic file. Not to say that > size is everything, but IMO VLDB comprises at least a TB, and often > many hundreds of TBs. -- -Francisco -- _______________________________________________ AccessD mailing list AccessD at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/accessd Website: http://www.databaseadvisors.com