What DB can handle more than 24 Indexes?

[Guest]

I've encountered a problem trying to link Access to a very old software
system that our sales force uses. The table has more than 24 indexes that I
want to link to, and access has a 24 index limit. Are there any other
Database programs that can handle more than 24 indexes? Which ones?

Thanks,
Billy

 

[Guest]

Try not to bring in the indexes but build your queries to to the same thing
by sorting

 

[Guest]

Try not to bring in the indexes but build your queries to to the same thing
by sorting.

 

[John Vinson]

I've encountered a problem trying to link Access to a very old software
system that our sales force uses. The table has more than 24 indexes that I
want to link to, and access has a 24 index limit. Are there any other
Database programs that can handle more than 24 indexes? Which ones?

Well, the limit in Access is actually 32 indexes, not 24. Do you
actually need Indexes? It's possible to query a table without an index
on the query field (though it will be inefficient and generally
undesirable, and you won't be able to enforce referential integrity).

Any chance you could move this data into a normalized multitable
structure?

John W. Vinson[MVP]

 

[Craig Alexander Morrison]

It is interesting to note that the 32 limit was imposed in Access 95 to make
Rushmore look better than it was and to stop Access competing too much with
SQL Server back in the days when SQL Server was still a ropey Windows port
from the SyBase product.

We had a system developed for London Underground in Access 1.1/2.0 that must
have had 50 or more relationships hanging from a few central tables, (back
then the 32 limit was for foreign key relationships aka lookups). The first
thing MS Consulting Services said was "it should be implemented on SQL
Server", if it was mission critical we would have used something bigger,
probably OS/2 and Database Manager. Note the current version of SQL Server
supports 255 indexes.

There is a kludgy but workable way to have more than 32 indexes on a major
table by creating a 1 to 1 relationship and moving the less frequently used
and optional fields into this table. This is not quite R however in the
"Elimination of Nulls" quest it could be argued not too wrong.

 

[Craig Alexander Morrison]

Correction SQL Server 2000 supports 249 non-clustered indexes and 1
clustered.