It would help to know what he thought multiple clustered indexes would help with ...

I never would have guessed that the primary key did not effect the row order in data pages in a non clustered table.

Up until this point I thought a index defrag on a non-clustered table reorged the data pages by primary key order. Stuck in the monotonically increasing primary key paradigm I guess. When would you want a primary key rather than a uniqueness constraint on a non clustered table ?

I am curious as to the difference between DB2 as SQL servers index implementation.

As the existing index pages fill and we get page splits are we saying DB2 and SQL server manage this differently ? I would have expected a new page to be allocated to the index linked between the two entries that previously bounded the new insert and the higher level index pages be updated recursively. Obviously I am missing something.