Which query insights view helps identify long-running queries in Fabric?

• A. queryinsights.exec_requests_history
• B. queryinsights.long_running_queries
• C. queryinsights.frequently_run_queries
• D. queryinsights.active_queries

Answer: (B)

When you need to spot queries that take a long time to run in Fabric, look for a view that specifically highlights long durations. The long_running_queries view is designed for this purpose, listing queries whose runtime exceeds a defined threshold and showing details like duration, start time, and the query text. This makes it easy to pinpoint slow operations and investigate possible causes such as inefficient joins, missing indexes, or resource contention, so you can optimize performance. Other views serve different needs: a history of executed requests covers general execution history rather than focusing on length; frequently_run_queries shows the most common queries, not how long they take; and active_queries shows what’s running now, which helps monitor load but doesn’t identify past long-running queries.