Indexes are ordered - period. As such, they are ascending or descending. They default to ascending and it is very rare you would set them to descending.
Quote:
Originally Posted by mishaalsy
so here in this index we have two sets of values . one starting from a to z . second starting from 1 to (max) numerics.
|
No - there is one set of values.
Quote:
Originally Posted by mishaalsy
does this cluster index not forcing full index SCAN of all the rows on every execution ?
|
Do you mean it is not possible to seek on this index? In that case - no you are wrong.
Quote:
Originally Posted by mishaalsy
while every new insert or bulk insert is tending it to rebuild again ( ? ) is it. ? (rebuild is my oracle terminology... recreating itself . )
in my test case it is .
|
No - not rebuilds, though I am using SQL Server terminology. Random inserts (as opposed to sequential ones) may cause page splits.
Note that NEWSEQUENTIALID() does generate sequential GUIDs, unlike NEWID() and would usually be used as the default for this sort of column.