You need in 0 indexes for 300 records. What you actually need is to build Order by clause on fly.

>Okay, one thing I failed to mention is that there will be NO updates done to the cursor. The indexes are strictly used to sort data in any way the user wishes for printing.
>
>This is a commercial baseball research project, and the largest cursor to be indexed will be 300 records, and frequently fewer than 10. Of course having 1,280 (and it might have to go as high as 1,500) indexes is overkill, but this is not a normal circumstance.
>
>Many of the indexes may never be used, but I cannot take for granted that SOME user will want to sort batters by fewest sacrifice flies and pitchers by most hit batsmen, and I have to have an index that will sort by player type (batter or pitcher), then sacrifice flies ascending, then hit batsmen descending. I also have to have an index that will sort the in opposite orders, one that will do both ascending, and a fourth to do both descending. Then I have to index on every other possible combination (20 batter categories, 16 pitcher), four times each, and also a few other simpler indexes as well.
>
>It's complicated and ultimately redundant, but I'm not worried about adding or updating records. I'm just concerned with the limits.