Hopefully, Troy and RJ and others will chip in here. They deal with
mega-row tables
Your 700 identical tables create a lot of "unwieldiness," too. It is quite
possible for you to create your very own autonumbering formula. In a
control table, containing a row of information about each of your 700
kinds of data, you can store an integer column representing a next
number. Steve Hartmann has a great technique for retrieving and
guaranteeing success at autonumbering that way.
As long as your retrieval is always based on indexed integer columns,
performance with a million rows need not be unwieldy. And you could
subdivide your data into 3 or 4 groups to get the size smaller if you
wanted to, and still have far far fewer programming and maintenance
headaches than you will have with 700 tables.
On Wed, 26 Sep 2001 08:19:35 -0700, Michael Young wrote:
>
>I guess at this point I could ask what is the maximum number of rows
that a
>table can accept and at what point does it become too unwieldy.?
