The point in question is that how many copies of data you want to keep...if it is one....you can store it in only one order physically.....now by definition a clustered index is associated with the physical order.....the index illustrated by EdVassie is merely a clustered index with two dimensions...

as Last Name, then First name in the case of an address book....wherein for his case it is type of object, then objectid or something.....these are basics friends.....

well....logically or functionally you can have n number of indexes at place for your database, but physically it depends upon how many copies of data you want to keep....

For more complex ways of data storage and retrieval, check out cubes in SQL Server Analysis Services.

It is good to argue, but it is useless if you don't accept.