Posted by Erland Sommarskog on 09/30/10 12:01

Gints Plivna (gints.plivna@gmail.com) writes:
> OK I've also tried it with much bigger table and got the same results
> as you. Let's hope optimizer will be smart enough to distinguish big
> work from small work and in case of big work won't do order before
> top :)

Since you are on SQL 2005, any reason to not use row_number()? Then
you would have code that would run both on SQL Server and on Oracle?


--
Erland Sommarskog, SQL Server MVP, esquel@sommarskog.se

Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/prodtechnol/sql/2005/downloads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodinfo/previousversions/books.mspx

[Back to original message]