SQL Server IN 与 EXISTS 性能

SQL Server IN vs. EXISTS Performance(SQL Server IN 与 EXISTS 性能)
本文介绍了SQL Server IN 与 EXISTS 性能的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我很好奇以下哪个更有效?

I'm curious which of the following below would be more efficient?

我一直对使用 IN 持谨慎态度,因为我相信 SQL Server 会将结果集转换为一个大的 IF 语句.对于大型结果集,这可能会导致性能不佳.对于较小的结果集,我不确定两者是否更可取.对于大型结果集,EXISTS 不是更有效吗?

I've always been a bit cautious about using IN because I believe SQL Server turns the result set into a big IF statement. For a large result set, this could result in poor performance. For small result sets, I'm not sure either is preferable. For large result sets, wouldn't EXISTS be more efficient?

WHERE EXISTS (SELECT * FROM Base WHERE bx.BoxID = Base.BoxID AND [Rank] = 2)

对比

WHERE bx.BoxID IN (SELECT BoxID FROM Base WHERE [Rank = 2])

推荐答案

EXISTS 会更快,因为一旦引擎发现命中,它会在条件被证明为真时停止查找.

EXISTS will be faster because once the engine has found a hit, it will quit looking as the condition has proved true.

EXISTS>

使用IN,它将在进一步处理之前收集子查询的所有结果.

With IN, it will collect all the results from the sub-query before further processing.

这篇关于SQL Server IN 与 EXISTS 性能的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持编程学习网!

本站部分内容来源互联网,如果有图片或者内容侵犯您的权益请联系我们删除!

相关文档推荐

Execute complex raw SQL query in EF6(在EF6中执行复杂的原始SQL查询)
SSIS: Model design issue causing duplications - can two fact tables be connected?(SSIS:模型设计问题导致重复-两个事实表可以连接吗?)
SQL Server Graph Database - shortest path using multiple edge types(SQL Server图形数据库-使用多种边类型的最短路径)
Invalid column name when using EF Core filtered includes(使用EF核心过滤包括时无效的列名)
How should make faster SQL Server filtering procedure with many parameters(如何让多参数的SQL Server过滤程序更快)
How can I generate an entity–relationship (ER) diagram of a database using Microsoft SQL Server Management Studio?(如何使用Microsoft SQL Server Management Studio生成数据库的实体关系(ER)图?)