Table capacity

We have a table with over 17,000 rows and haven’t ran into any issues.

Steve

One and All,

I understand that Cloverleaf will use a “binary search algorithm” for large tables, that is, break it up into searchable sections and step thru each trying to find the entry by dividing it into halves and narrowing it down to where the entry ought to be (I know not a very scientific explanation).   This is not a new method – as a Cobol programmer in a former life we could specify binary type searches on large tables.

Right now we have a table of departments that exceeds 17,500 entries and so far no issues.

Enjoy.

BobR

A long time ago I was told by Larry Streepy that they use a very efficient hashing algorithm for Tables.

Knowing Streepy and those guys somewhat I can believe it.

Anyway at one time in a previous life we had a table with 30,000+ entries and again no problem – on a relatively small AIX platform.

The biggest issue with very large tables in my opinion is maintenance. In our table, the actual table was maintained by the system of truth then exported from the DB, FTP’d to Cloverelaf where a Tcl proc I wrote built the table from the delimited file, maintained backups, and purged caches on a scheduled basis.