SQL Server Paging - The Holy Grail
More info on the above see SqlServerCentral Another version:
Posts
Interpreting the query plan and speeding it up
Bookmark Lookup - An index was used but as the index does not 'cover' the query the query processor must use the ROWID from the index to 'lookup' the actual data row. Unless the index can be alter to ‘cover’ the columns of the query this cannot be optimised further. Clustered Index Scan - Similar to a table scan (its just that the table has a clustered index) and similarly undesirable, particularly for large tables. If you see these then the columns in the query are either not indexed or the distribution statistics have led the query optimiser to decide the scan is more/ as efficient. Restructuring the query can sometimes eliminate these operations; or add an index. Clustered Index Seek - The clustered index is used to find matching rows. This is optimal behaviour. Compute Scalar - As it says – a scalar is being computed. Unless this is not really needed it can't be optimised. It its not needed, remove it! Constant Scan - The query requires a constan...