是否有工具来分析sqlite查询？-Isthereatooltoprofilesqlitequeries?

20  

You have a mix of questions in here. To view what queries are run and how long each takes, you'll need to either modify sqlite3.dll if an application is linking to that or if it's your own application you can write it into your code easier (we do this and long all queries, transactions, timings, etc.).

你在这里有各种各样的问题。要查看运行的查询以及每个查询需要多长时间，您需要修改sqlite3.dll（如果应用程序链接到该应用程序）或者如果它是您自己的应用程序，则可以更轻松地将其写入代码中（我们这样做并且很长时间查询，交易，时间等）。

For individual query analysis, you can use EXPLAIN. It won't tell you timing of individual steps within a query but it will tel you how the query was executed.

对于单个查询分析，您可以使用EXPLAIN。它不会告诉您查询中各个步骤的时间，但它会告诉您查询的执行方式。

http://www.sqlite.org/lang_explain.html

http://www.sqlite.org/lang_explain.html

An SQL statement can be preceded by the keyword "EXPLAIN" or by the phrase "EXPLAIN QUERY PLAN". Either modification causes the SQL statement to behave as a query and to return information about how the SQL statement would have operated if the EXPLAIN keyword or phrase had been omitted.

SQL语句前面可以是关键字“EXPLAIN”或短语“EXPLAIN QUERY PLAN”。这两种修改都会导致SQL语句表现为查询，并返回有关如果省略EXPLAIN关键字或短语后SQL语句将如何操作的信息。

When the EXPLAIN keyword appears by itself it causes the statement to behave as a query that returns the sequence of virtual machine instructions it would have used to execute the command had the EXPLAIN keyword not been present. When the EXPLAIN QUERY PLAN phrase appears, the statement returns high-level information about what indices would have been used.

当EXPLAIN关键字本身出现时，它会使该语句表现为一个查询，该查询返回如果没有EXPLAIN关键字，它将用于执行命令的虚拟机指令序列。当EXPLAIN QUERY PLAN短语出现时，该语句返回有关将使用哪些索引的高级信息。

The output from EXPLAIN and EXPLAIN QUERY PLAN is intended for interactive analysis and troubleshooting only. The details of the output format are subject to change from one release of SQLite to the next. Applications should not use EXPLAIN or EXPLAIN QUERY PLAN since their exact behavior is undocumented, unspecified, and variable.

EXPLAIN和EXPLAIN QUERY PLAN的输出仅用于交互式分析和故障排除。输出格式的详细信息可能会从SQLite的一个版本更改为下一个版本。应用程序不应使用EXPLAIN或EXPLAIN QUERY PLAN，因为它们的确切行为是未记录的，未指定的和可变的。

32  

This will only answer one part of the question (the most unhelpful part, unfortunately).

这只会回答问题的一部分（不幸的是，这是最无益的部分）。

I googled this up because I was looking for something to time queries and the sqlite3 client has a timer meta command.

我搜索了这个因为我正在寻找时间查询的东西，而sqlite3客户端有一个计时器元命令。

sqlite> .timer on

sqlite> .timer

from there on in, all query results will have cpu timer statistics appended. Hope this helps at least a little bit.

从那里开始，所有查询结果都会附加cpu计时器统计信息。希望这有助于至少一点点。

2  

Now SQLite has experimental sqlite3_trace and sqlite3_profile (see https://www.sqlite.org/c3ref/profile.html for details). They can come in handy for having statistics/investigating culprit during long tests.

现在SQLite有实验性的sqlite3_trace和sqlite3_profile（详见https://www.sqlite.org/c3ref/profile.html）。在长时间的测试中，他们可以派遣统计/调查罪魁祸首。