Re: Big Tables? Real Life Examples.....

We used to have a table of 2.5 billion rows. If you design it right and give each row a unique id and index it right, there is no problem with it.

If you are worried about full table scans, then you don't need that size to kill your system. You should not allow FTS to happen when table gets that big. If you do, because typically the big tables have very high insertion rate, you may get snapshot too old anyway.

You can use partitions too. It will cut down your index depth and reduce query cost. Received on Mon Jul 04 2005 - 12:03:52 CDT