"Where the Time Actually Goes"

1. What are the four places where time can hide in a slow report?

The SQL itself Waiting Result-set transfer All of the above

2. If a report's performance is fast in SSMS but slow in the application, what does this indicate?

The server is busy and needs optimization The time is in result-set transfer or client-side rendering The query lacks proper indexing The SQL statement is poorly written

3. Which SQL command will provide statistics that separate CPU time from elapsed time?

SET STATISTICS IO ON SET STATISTICS TIME ON TRACE ON EXECUTE STATISTICS

4. What initial questions should you ask when investigating a report's performance issue?

Is the report making use of indexes? What hardware is being used? Slow always, or slow sometimes? How often is the database being backed up?

Continue: "Query Store: Your First Stop" → Review this lesson Retake quiz