hey,

nobody said you had been tripped up... in fact I said that I had been tripped up before

in sql 2000 days people always said PHYSICAL storage order. most likely...

I've been tripped up by this before too

The key point is PHYSICAL .

A clustered index does not determine the order it is stored on disk.

I went to a lecture...

lets be clear on that point....

a clustered index does not prevent duplicates

a primary key (normally also the clustered index) or also a unique constraint will prevent duplicates

the clustered index is...

this is the first one I came across on google

http://gruffcode.com/2012/06/21/using-table-valued-parameters-with-sql-server-reporting-services/

why not use a TABLE VALUE PARAMETER in your stored proc

simply use the CREATE TYPE statement (to create a table type), then create your proc using the table type as...