Search box in SSMS Object Explorer
Please add a search box in SSMS Object Explorer similar to what Visual Studio has in the Solution Explorer! It should include autocomplete and the robust filtering abilities (by database, by object type, by schema)
It is extremely slow to constantly have to navigate through the tree to find the objects you want. I just want to type where I want to go.
Object Explorer doesn’t populate the entire tree in memory, unlike visual studio’s solution explorer. It wouldn’t know if database “MyDatabase” existed until you expanded the Databases node.
There are third party plugins that provide this type of functionality, I believe, by downloading a bunch of data in the background and exposing a search.
Marcus Koch commented
This is one of the most frustrating things in SMS. It drives me insane every day. Maybe the product team of SMS should google the term "mental sanity".
Sorry, but the excuse for not having this feature is really lame! Is this a professional database tool or a toy?
Andrei Rantsevich commented
SOLUTION: (until not implemented natively)
We have added this to SSMSBoost add-in (www.ssmsboost.com).
"Advanced objects search" feature has a small, dockable pane, which can be docked above or below Object Explorer. It has "search on the fly" edit box, which performs the search through all objects in the current database or even server. When desired object is found, you can click "Locate in Object Explorer", which will expand it's node in Object Explorer and make it active.
I can search the entire world wide web from a single text box but to find an object in SSMS takes several mouse clicks.
Why not add an object search text box that is linked to the currently selected database, with some simple syntax like "table:myobjname", with this the time to find an object could be greatly reduced.
I probably filter by object name twenty times a day so this would be a meaningful time saver for me.
When you open a new server connection, you can select the "Databases" folder and then use the filter button at the top to filter the list. Alternatively, right-click on "Databases" and click "Filter". There is apparently no need to expand the list first.
It would be nice if we could use a keyboard shortcut such as Ctrl+F to open the filter dialog. But even with that, we couldn't apply the filter without using the mouse or hitting Tab a bunch of times to select the "Contains" field and then the "Okay" button.
Eric Renken commented
Doesn't almost everyone expand out the database list anyway? We use SQL Azure DBs and Elastic Pools. I have about 5,000 DB on one server. I NEED a fast way to search for databases. You basically have it when I click on Databases I can click the filter button and enter a name to value for the name contains. Why can't you just take this to a higher level, so I don't have to click on the filter button and open this big dialog?
"Object Explorer doesn’t populate the entire tree in memory, unlike visual studio’s solution explorer"
So? This doesn't seem like a very big problem.
Make it asynchronously load the entire tree when the application starts so you can have a decent search. This is zero reason why doing this is not possible.
Having a great user experience (through search capabilities) is much more important than trying to make performance decisions on your customers behalf.
How this can be possible with SQL Operation Studio?
seriously! only 12 votes? would a built in function not be so much better than a 3rd party add-on?