在这个示例中，因为希望对单一交易的状态执行只读查询，显然应该使用GET方法，使用的URI模式见清单4。
In this case, because you want to perform a read-only lookup of the status of a single transaction, the GET method is an obvious fit using the URI pattern, as shown in Listing 4.
通过 HResult，执行模式可以在单个运行树中结合MDX和XML，实现更高的灵活性和查询性能。
With HResult the execution mode can combine MDX and XML in a single run tree, allowing for much higher flexibility and query performance.
以任一查询模式执行这个报告时，报告都显示Salesregions和Country嵌套为行，Quantit y度量值数据嵌套为列。
When this report is executed in either query mode, the report displays the Sales regions and country nested as the rows and the Quantity measure as the columns.
因此，除非以high模式运行，否则UPDATESTATISTICS与执行查询本身是不能相提并论的。
Therefore, UPDATE STATISTICS cannot be compared to executing the query itself unless it is run in the high mode.
Repository类使用了上述的抓取模式来执行查询，如下代码所示。
The repository class USES the above fetching pattern to retrieve the query that needs to be executed as shown in the sample code below.
这些例子演示如何注册XML模式、如何执行 XML实例文档验证，以及如何使用XQuery或SQL/XML查询 XML数据等。
The examples show how to register an XML Schema, how to perform validation of XML instance documents, how to query XML data using XQuery or SQL/XML and much more.
结果：多次执行查询从后端返回数据，这是因为整个会话的read-levelpassthrough模式都被设置为 FORCE。
Result: Executing the query multiple times returns the data from the back end. This is because the read-level passthrough mode is set to FORCE for the whole session.
在这些情况下，在初次执行收集时，您将对MBeanServerConnection发起一个查询，并请求与提供模式相匹配的所有MBeans的列表。
In these cases, the first time you make a collection, you issue a query against the MBeanServerConnection and request a list of all the MBeans that match the supplied pattern.
开始本教程之前，执行这些模式查询以在DB 2中创建一个数据库。
Execute these schema queries for creating a database in DB2 before starting the tutorial.
在异步模式下，提交的查询在以后某个时候执行，也可能重复执行。
In the asynchronous mode, the query is submitted for a later, possibly repeated, execution.
类似的，对不同模式执行查询可能得到下面的结果。
Likewise, evaluating queries on different schemas might result in the following outcomes.
其中，dbname指定了执行查询的数据库，input .txt指定了SQL查询的输入文件，cli指定了在cli模式下运行，out put .txt指定了db 2 batch命令结果导向的文件。
Where, dbname specifies the database to run the queries against, input.txt specifies the input file with your SQL queries, cli specifies to run in cli mode, output.txt?
如果认为并行执行查询将带来加速，则使用此标志，但处于默认模式的PLINQ将按顺序执行它。
Use this flag in cases where you know that parallel execution of the query will result in speedup, but PLINQ in the Default mode would execute it as sequential.
不过，有时候经由测试和测量，您可能会发现某个查询在非预设模式下的执行效能最佳。
However, in some cases you may find by testing and measurement that a query executes best in a non-default mode.
根据这项分析，在预设执行模式下的PLINQ可能会决定以循序方式执行局部或整个查询。
Based on this analysis, PLINQ in the default execution mode may decide to execute some or all of the query sequentially.
本文从包含查询接口、结果模式和映射规则的包装器描述文件(XML)出发，给出了自动生成可执行代码的技术方案。
Wrapper description incorporates the query interfaces, result schemas and mapping rules. This XML file is used to generate executable code automatically.
用户可一次处理数个查询，通过几种模式编辑查询，观察运算结果，以及执行任何其它需要的操作。能查看查询计划。
You can work with several queries at once, edit queries and view the execution results in several modes and perform any other operations you may need in your work with database queries.
用户可一次处理数个查询，通过几种模式编辑查询，观察运算结果，以及执行任何其它需要的操作。能查看查询计划。
You can work with several queries at once, edit queries and view the execution results in several modes and perform any other operations you may need in your work with database queries.
应用推荐