|
|
|
|
|
by nvivo
2956 days ago
|
|
I think it's different. From the docs, this is a one time update to the table. The table itself is not clustered, it's just ordered based on a clustered index, so selects by default should come in that order. But once an insert is done, it's again ouy of order. Also, an order by using the cluster field most probably invokes an index scan, while a clustered table doesn't. |
|