No, it seems that you don't understand what a clustered index is...
Put simple, when you have a table with a non-clustered index, the rows are put in the order you insert them.
If your script insert rows with the order: "10,8,6,9,1,7,3,5,2,4", then inspecting the pages (physical allocation on disk) we would find the rows in that order.
If your table have an clutered index, then sql server will reorganize the rows upon insertion to put them in the order defined by the index.
So, if like previously, you insert the rows with the order "10,8,6,9,1,7,3,5,2,4", we would find them ordered from 1 to 10.
So, in my opinion, you cannot emulate an clustered index without a clustered index without having a serious performance hit.
The only solution I see would be to have a trigger that would fetch the whole table in a temp table, and redo an insert with a
Code:
insert into tableX(x, y, z)
select x,y,z
from #tmpTable
order by id
on each insert.
I cannot say that I'd encourage this....
