另一个例子:

declare @limit int 
declare @offset int 
set @offset = 2;
set @limit = 20;
declare @count int
declare @idxini int 
declare @idxfim int 
select @idxfim = @offset * @limit
select @idxini = @idxfim - (@limit-1);
WITH paging AS
    (
        SELECT 
             ROW_NUMBER() OVER (order by object_id) AS rowid, *
        FROM 
            sys.objects 
    )
select *
    from 
        (select COUNT(1) as rowqtd from paging) qtd, 
            paging 
    where 
        rowid between @idxini and @idxfim
    order by 
        rowid;

另一个例子:

declare @limit int 
declare @offset int 
set @offset = 2;
set @limit = 20;
declare @count int
declare @idxini int 
declare @idxfim int 
select @idxfim = @offset * @limit
select @idxini = @idxfim - (@limit-1);
WITH paging AS
    (
        SELECT 
             ROW_NUMBER() OVER (order by object_id) AS rowid, *
        FROM 
            sys.objects 
    )
select *
    from 
        (select COUNT(1) as rowqtd from paging) qtd, 
            paging 
    where 
        rowid between @idxini and @idxfim
    order by 
        rowid;

因为，我测试了更多次这个脚本更有用的100万条记录，每页100条记录分页工作更快，我的PC执行这个脚本0秒，而与mysql相比有自己的限制和偏移约4.5秒得到结果。

有些人可能不理解Row_Number()总是按特定字段排序。如果我们只需要按顺序定义行，应该使用:

Row_number () over (order by (select null))

SELECT TOP {LIMIT} * FROM (
      SELECT TOP {LIMIT} + {OFFSET} ROW_NUMBER() OVER (ORDER BY (SELECT NULL)) AS ROW_NO,*
      FROM  {TABLE_NAME}
) XX WHERE ROW_NO > {OFFSET}

解释:

{LIMIT}:每页的记录数 {OFFSET}:跳过记录的个数

我假设，在c#表达式/LINQ语句的跳过和采取生成下面的SQL命令

DECLARE @p0 Int = 1
DECLARE @p1 Int = 3
SELECT [t1].[Id]
FROM (
    SELECT ROW_NUMBER() OVER (ORDER BY [t0].[Id]
    FROM [ShoppingCart] AS [t0]
    ) AS [t1]
WHERE [t1].[ROW_NUMBER] BETWEEN @p0 + 1 AND @p0 + @p1
ORDER BY [t1].[ROW_NUMBER]

LIMIT的等效函数是SET ROWCOUNT，但是如果你想要通用的分页，最好这样写一个查询:

;WITH Results_CTE AS
(
    SELECT
        Col1, Col2, ...,
        ROW_NUMBER() OVER (ORDER BY SortCol1, SortCol2, ...) AS RowNum
    FROM Table
    WHERE <whatever>
)
SELECT *
FROM Results_CTE
WHERE RowNum >= @Offset
AND RowNum < @Offset + @Limit

这里的优点是，如果您决定更改分页选项(或允许用户这样做)，则可以将偏移量和限制参数化。

注意:@Offset参数应该使用基于1的索引，而不是普通的基于0的索引。

因为还没有人提供这个代码:

SELECT TOP @limit f1, f2, f3...
FROM t1
WHERE c1 = v1, c2 > v2...
AND
    t1.id NOT IN
        (SELECT TOP @offset id
         FROM t1
         WHERE c1 = v1, c2 > v2...
         ORDER BY o1, o2...)
ORDER BY o1, o2...

重要的几点:

ORDER BY必须相同 @limit可以替换为检索结果的数量， @offset是要跳过的结果数 请将性能与以前的解决方案进行比较，因为它们可能更有效 这个解决方案重复了where和order by子句，如果它们不同步，将提供不正确的结果 另一方面，如果需要的话，order by是明确存在的