This is true only if you have a clustered index. Otherwise, you have no control on the natural order of records.

>SQL naturally stores data in the primary sequence to improve speed. It even leaves gaps if you tell it to so inserting becomes quicker.
>
>>We have an app that utilizes several VFP tables that are about 200-600 MB in size (a few million records.)
>>
>>Queries hit these tables every day, so we try to keep the physical order reflective of the queries (i.e. physical order is in acct/item/date order). This makes a BIG impact on queries.
>>
>>However, we soon will be 'upsizing' to SQL Server. Anyone familiar with what happens then? In other words, are queries against back-end SQL Server databases as sensitive to the physical order as VFP databases appear to be? (I guess the question gets to the root of the indexing structure, and I know nothing about how SQL Server handles it).
>>
>>TIA,
>>Kevin