1

所以我遇到了一个严重的麻烦，因为我的最后一个查询执行时间是 8 分钟才能获得 2500 个节点。它只是结合了其他两种观点。

第一个观点是：

SELECT
   RecTime, SQL AS str, ID, 
   ROW_NUMBER() OVER(ORDER BY RecTime,ID) AS rwnb 
FROM         
   (SELECT
       A.RecTime, X.SQL, X.ID
    FROM 
       dbo.EventView AS A 
    CROSS JOIN
       dbo.Incident AS X
    WHERE      
       (PATINDEX('%' + A.Col + '%', X.SQL) > 0)) AS INC

1 秒和 1600 个节点

第二种观点是：

SELECT     
   D.RecTime, D.Event, D.ID, CAST(CASE WHEN X.[Value] IS NULL THEN 0 ELSE X.[Value] END AS bit) AS Value
FROM         
   dbo.XDependencedEvents AS D 
INNER JOIN
    dbo.EventView AS X ON X.Col = D.Event 
                          AND D.RecTime BETWEEN X.RecTime AND X.ChangedDate

3秒执行时间和2100个节点

最后的观点是

SELECT 
    X.[Rectime], X.[ID], X.[str], D.[Event], D.[Value],X.[rwnb] 
FROM 
    [XDependencedIncidents] AS X
INNER JOIN [XEventStates] AS D ON X.[Rectime] = D.[Rectime]
                                  AND X.[ID] = D.[ID]

8 分钟和 2500 个节点。

我什至使用 RowNumber AS rwnb 来加快处理视图的速度，但它仍然非常慢。我必须在前 2 个视图中使用 select into temp 表吗？或者我在这里做错了什么？

最终目的是在每次“事件”发生变化时为“事件”的某些“组”获取值

4

2 回答 2

1

尝试这个：

SELECT X.[Rectime] , X.[ID] , X.[str], D.[Event], D.[Value],X.[rwnb] 
FROM [XDependencedIncidents] AS X
INNER JOIN [XEventStates] AS D ON X.[ID] = D.[ID]
WHERE X.[Rectime] = D.[Rectime]

如果它也很慢。检查XEventStates Indexing.

于 2011-04-18T05:37:03.670 回答
0

我奇怪的解决方案是使用 RowNumber 修改第二个和最后一个视图，如：

SELECT     D.RecTime, D.Event, D.ID
,CAST(CASE WHEN X.[Value] IS NULL THEN 0 ELSE X.[Value] END AS bit) AS Value
,ROW_NUMBER() OVER(ORDER BY D.RecTime,D.ID) AS rwnb 
FROM         dbo.XDependencedEvents AS D 
    INNER JOIN
    dbo.EventView AS X 
        ON X.Col = D.Event 
        AND D.RecTime BETWEEN X.RecTime AND X.ChangedDate

和

SELECT X.[Rectime] , X.[ID] , X.[str], D.[Event], D.[Value],X.[rwnb], D.[rwnb]
FROM [XDependencedIncidents] AS X
INNER JOIN [XEventStates] AS D ON X.[ID] = D.[ID]
AND X.[Rectime] = D.[Rectime]

您如何看待这种奇怪的优化方法？如果有的话，我真的想要一个更好的解决方案。

顺便说一句，是的，添加行号需要 8 分钟 -> 5 秒。

于 2011-04-18T06:02:06.143 回答