tag:blogger.com,1999:blog-5941051.post112919601911767550..comments2023-09-27T12:00:01.246+02:00Comments on EXEC dbo.LongTermMemory__Archive: NOLOCK vs Clustered Index Order Part IVWesleyBhttp://www.blogger.com/profile/16615300015221548858noreply@blogger.comBlogger2125tag:blogger.com,1999:blog-5941051.post-1129910728763222032005-10-21T18:05:00.000+02:002005-10-21T18:05:00.000+02:00Thanks for the comment Mike.It's seems to be indee...Thanks for the comment Mike.<BR/>It's seems to be indeed the order of the physical placement. I'm waiting for an answer of one of the SQL Engine developers with more details... I'll post his answer as soon as I get it (if I get it of course :p)<BR/><BR/>Hmm... let me add a SQL Nerd to my BlogRoll ;)WesleyBhttps://www.blogger.com/profile/16615300015221548858noreply@blogger.comtag:blogger.com,1999:blog-5941051.post-1129779065965953012005-10-20T05:31:00.000+02:002005-10-20T05:31:00.000+02:00I'm going to hazard a guess that, based on your Pa...I'm going to hazard a guess that, based on your Part III & Part IV blogs, with the NOLOCK hint, the data is scanned in physical page order.<BR/><BR/>So in a heap, the order would be the same because the data returned from a plain "select * from dbo.foo" would do a table scan in physical page order (same as WITH (NOLOCK)) as there is no logical page order (it's unsorted data).<BR/><BR/>With a Mike Hodgsonhttps://www.blogger.com/profile/00652597391400615449noreply@blogger.com