嵌入式查询与命名查询 [英] Embedded Queries vs Named Queries

问题描述

Hello开发人员，

Hello fellow developers,

我想知道Microsoft Access报告中嵌入式查询和命名查询的优缺点。或者更具体地说，在哪些条件下更好地使用命名查询而不是嵌入式查询。是否比另一个更加CPU密集
？

I would like to know what are the advantages and disadvantages of embedded queries and named queries in a Microsoft Access report. Or more specifically, under which conditions is better to use a Named Query instead of an Embedded Query. Is one more CPU intensive than the other?

我已经发现使用嵌入式查询时，某些条件格式选项（如日期栏）不可用。

I have already discovered that some options of Conditional Formatting (such as Date Bars) are not available when using an Embedded Query.

非常感谢您的考虑。

推荐答案

"嵌入式"查询将与对象一起传输（导入/导出），因此我认为它可以被认为是一个优势。

"Embedded" queries will transfer (import/export) with the object, so it could be considered as an advantage, I guess.

我不认为你使用的执行时间有什么不同一个查询另一个。过去，您需要一个已保存（命名）的查询，因为它已经有一个执行计划。但是，如果您使用参数查询，那么它与
相同;此外，现在使用更快的计算机，这并不重要。

I don't think there is any difference in execution time whether you use one query over another. Used to be, you would want a saved (named) query because it will have an execution plan already. However, if you use parameter queries, then it doesn't work the same; plus, with faster computers now, it doesn't really matter.

只需2美分......

Just my 2 cents...

这篇关于嵌入式查询与命名查询的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！