SQL Server Management Studio – New Feature – Object Explorer Query Tracking

Object Explorer Query Tracking exposed SSMS queries while expanding nodes in the historical release. I used its Output window for investigation.

An open workshop door exposes its latch linkage beside an inspection lens.

In that release, I opened View > Output, then expanded the Databases node in Object Explorer. The output showed the query used for the expansion and its elapsed time. That gave me a useful lead when a node was slow or returned an error.

Original SSMS View menu used to open the Output window.
Original SSMS View menu used to open the Output window.
Original Output-window query and timing from expanding an Object Explorer node.
Original Output-window query and timing from expanding an Object Explorer node.

This demonstrates the 2017 SSMS release. Current Output categories and diagnostics depend on the installed build. Check those categories before expecting identical messages.

The feature didn’t capture node Properties-dialog queries. It also wasn’t a general workload profiler. I kept the query, error and timing together when investigating expansion. Server-side evidence helps confirm what happened.

Related reading

Object Explorer tracking is not a workload profiler, it is a diagnostic for the supported UI activity.

Published by Pinal Dave on SQLAuthority. More of my work at pinaldave.com.


Discover more from SQL Authority with Pinal Dave

Subscribe to get the latest posts sent to your email.

SQL Scripts, SQL Server, SQL Server Management Studio
Previous Post
SQL SERVER – Cluster Patching: The RPC Server is Too Busy to Complete This Operation
Next Post
Asking a SQL Question That Gets Answered: The Reproducible Script

Related Posts

2 Comments. Leave new

Leave a Reply

Your email address will not be published. Required fields are marked *

Fill out this field
Fill out this field
Please enter a valid email address.