有一个名为ANY 的undocumented aggregate 语法无效,但可能会出现在您的执行计划中。然而,这并没有提供任何性能优势。
假设如下表和索引结构
CREATE TABLE T
(
id int identity primary key,
[group] char(1)
)
CREATE NONCLUSTERED INDEX ix ON T([group])
INSERT INTO T
SELECT TOP 1000000 CHAR( 65 + ROW_NUMBER() OVER (ORDER BY @@SPID) % 3)
FROM sys.all_objects o1, sys.all_objects o2, sys.all_objects o3
我还填充了示例数据,因此每组有很多行。
您的原始查询
SELECT MAX(id),
[group]
FROM T
GROUP BY [group]
给出Table 'T'. Scan count 1, logical reads 1367和计划
|--Stream Aggregate(GROUP BY:([[T].[group]) DEFINE:([Expr1003]=MAX([[T].[id])))
|--Index Scan(OBJECT:([[T].[ix]), ORDERED FORWARD)
重写以获得ANY 聚合...
;WITH cte AS
(
SELECT *,
ROW_NUMBER() OVER (PARTITION BY [group] ORDER BY [group] ) AS RN
FROM T)
SELECT id,
[group]
FROM cte
WHERE RN=1
给出Table 'T'. Scan count 1, logical reads 1367 和计划
|--Stream Aggregate(GROUP BY:([[T].[group]) DEFINE:([[T].[id]=ANY([[T].[id])))
|--Index Scan(OBJECT:([[T].[ix]), ORDERED FORWARD)
尽管 SQL Server 可能会在找到第一个值后立即停止处理该组并跳到下一个值,但它不会。它仍然处理所有行并且逻辑读取是相同的。
对于这个组中有许多行的特定示例,更有效的版本将是递归 CTE。
WITH RecursiveCTE
AS (
SELECT TOP 1 id, [group]
FROM T
ORDER BY [group]
UNION ALL
SELECT R.id, R.[group]
FROM (
SELECT T.*,
rn = ROW_NUMBER() OVER (ORDER BY (SELECT 0))
FROM T
JOIN RecursiveCTE R
ON R.[group] < T.[group]
) R
WHERE R.rn = 1
)
SELECT *
FROM RecursiveCTE
OPTION (MAXRECURSION 0);
这给了
Table 'Worktable'. Scan count 2, logical reads 19
Table 'T'. Scan count 4, logical reads 12
逻辑读取要少得多,因为它检索每个组的第一行然后寻找下一个组,而不是读取对最终结果没有贡献的大量记录。