John..

Every table in SQL Server should have a clustered index. And...a table can only have 1 clustered index. At the minimum, one index should be designated as the clustered index - the way the records are physically stored. Most likely, there will need to be other indexes - or indices (are both correct?).

A good idea is to run the ODBC logging utility, grab the SQL that is being rendered, and run that SQL, using the query analyzer, using the performance analyzer tool. If there are any table scans, that will be the clue that an index is required...



>All
>
>>>Check the indexes on your backend. If you are using SQL Server, do you have a clustered index?<<
>
>JVP raises a good point, but there is a quite a lot to this. Commands like REINDEX against clustered indices can reorganise in the interests of efficiency. You can check the Consistency of your data to measure this- performance is definitely affected if your data is scattered widely wrt the main search index.
>
>Before adding clustered indexes willy nilly, however, I recommend that people call on highly expert advisors. Those of my customers who do this consider it money well-spent.
>
>Regards
>
>JR