An SQL query is a statement sent to a database management system to retrieve or modify data. Applications may write queries directly or generate them through persistence frameworks. section 6.0 section 6.3.2
SQL queries become an investigative concern when an application lags, times out, or behaves inefficiently. Profiling reveals which queries execute, how long they take, how often they run, and which application code sent them. section 6.3 section 6.4
A practical query investigation asks:
- Which endpoint or operation triggers the query? section 6.3.1
- How many times does the query execute, and does that match the application logic? section 6.3.1
- Which call stack and framework operation produced it? section 6.3.2
- Can the captured query be copied into a SQL client for further investigation? section 6.3.2
Finding repeated product lookups
Calling /products returns purchased product names. The application first loads purchases, then calls findProduct() for each purchase. Profiling exposes the executed SQL, its stack trace, and its invocation count; ten repository calls may reveal an inefficient access pattern. With native JDBC, the query can appear directly as SELECT * FROM product WHERE id = ?. With Spring Data JPA and Hibernate, profiling still captures the generated SQL before it reaches the DBMS, while logging can show bound parameters and extracted values. section 6.3.1 section 6.3.2
