下面是常用的分頁,及其分頁效率分析。
1.分頁方案一:(利用Not In和SELECT TOP分頁)
語句形式:
- SELECT TOP 10 *
- FROM TestTable
- WHERE (ID NOT IN
- (SELECT TOP 20 id
- FROM TestTable
- ORDER BY id))
- ORDER BY ID
- SELECT TOP 頁大小 *
- FROM TestTable
- WHERE (ID NOT IN
- (SELECT TOP 頁大小*頁數 id
- FROM 表
- ORDER BY id))
- ORDER BY ID
2.分頁方案二:(利用ID大于多少和SELECT TOP分頁)
語句形式:
- SELECT TOP 10 *
- FROM TestTable
- WHERE (ID >
- (SELECT MAX(id)
- FROM (SELECT TOP 20 id
- FROM TestTable
- ORDER BY id) AS T))
- ORDER BY ID
- SELECT TOP 頁大小 *
- FROM TestTable
- WHERE (ID > (SELECT MAX(id)
- FROM (SELECT TOP 頁大小*頁數 id
- FROM 表
- ORDER BY id) AS T))
- ORDER BY ID
3.分頁方案三:(利用SQL的游標存儲過程分頁)
- createprocedure SqlPager
- @sqlstr nvarchar(4000),
- @currentpage int,
- @pagesize int
- as
- set nocount on
- declare @P1 int,
- @rowcount int
- exec sp_cursoropen @P1 output,@sqlstr,@scrollopt=1,@ccopt=1,@rowcount=@rowcount output
- select ceiling(1.0*@rowcount/@pagesize) as 總頁數
- set @currentpage=(@currentpage-1)*@pagesize+1
- exec sp_cursorfetch @P1,16,@currentpage,@pagesize
- exec sp_cursorclose @P1
- set nocount off
其它的方案:如果沒有主鍵,可以用臨時表,也可以用方案三做,但是效率會低。
建議優化的時候,加上主鍵和索引,查詢效率會提高。
通過SQL 查詢分析器,顯示比較:我的結論是:
分頁方案二:(利用ID大于多少和SELECT TOP分頁)效率最高,需要拼接SQL語句
分頁方案一:(利用Not In和SELECT TOP分頁) 效率次之,需要拼接SQL語句
分頁方案三:(利用SQL的游標存儲過程分頁)效率最差,但是最為通用