Here you have a lot of questions. To see what queries are being executed and how long it will take, you need to either change sqlite3.dll if the application refers to this, or if your own application you can write it to your code easier (we do this all the time, requests, transactions, timings etc.).
For individual query analysis, you can use EXPLAIN . It will not tell you the time frame of the individual steps in the request, but it will tell you how the request was completed.
http://www.sqlite.org/lang_explain.html
The SQL statement may be preceded by the keyword "EXPLAIN" or the phrase "EXPLAIN QUERY PLAN". Any modification causes the SQL statement to behave like a query and return information about how the SQL statement would work if the EXPLAIN keyword or phrase was omitted.
When the EXPLAIN keyword appears on its own, it forces the operator to behave like a query that returns the sequence of virtual machine commands that it would use to execute the command if the EXPLAIN keyword were not present. When the phrase EXPLAIN QUERY PLAN appears, the statement returns high-level information about which indexes would be used.
Exiting EXPLAIN and EXPLAIN QUERY PLAN is for interactive analysis and troubleshooting only. Details of the output format can be changed from one SQLite release to another. Applications should not use EXPLAIN or EXPLAIN QUERY PLAN, since their exact behavior is undocumented, undefined, and variable.
Samuel Neff Jul 08 '10 at 21:56 2010-07-08 21:56
source share