I was using various “quick find” SSMS add-ins which give you ability to get your tables, stored procedures, functions and other objects quicker than by using standard SSMS features. Few of them were very well usable but all of them are built to support also complex searching including schema, source code occurence, object type etc. etc. This is basically good feature but if you’re inside furious T-SQL coding you just want to jump accross objects with quickest way possible – every filter criteria or detail you must take care of is slowing you down.
This is the ideal situation for me:
1) press e.g. CTRL+T to bring tiny search window
3) enter part of object’s name
4) choose object and press ENTER to bring ALTER script or open window where this object is already opened
I prepared prototype of add-in which perfectly fulfills my requirements, sample screenshot is here:
Here is also short video showing some more use cases.
Feel free to comment.
Tags: Add-In, filter criteria, quick find, search, search window, SQL, SSMS, SSMS Add-In, Stored procedure, t-sql

I downloaded the SQLTreeO, but is the Search Add In a separate download? I don’t see the link. After installing SQL TReeO, Control T has no effect.
Hi,
Search add-in is not part of SqlTreeo currently. I’am using this add-in only for my personal usage yet. I will probably incorporate it in SqlTreeo in the future.
Jakub
Thanks for the reply Barney, that cleared most tnighs up for me, and I seem to have it working so that is creates a schema_version table in whatever application I have it in, I am really impressed with how this could potentially work. However I am still unclear as to how to run the scripts in the directory that is specified, for some reason I can’t get these to run, even with the demo. The line I am using in Application.cfm is below, this creates the schema_version fine but does not run the demo scripts which I have put in a schema_scripts directory to test.createObject(“component”, “schema_tool.tool”).init(application.config.dsn, “cms.schema_scripts”).ensureCurrent(“#application.applicationname#.schema_tool”);Both schema_tool and cms are mapped locations. Any help would be much appreciated.
This sounds exactly like what I’m looking for as well. Any news on releasing this yet? I’d be glad to try a pre-release version!
Hi,
I am still experiencing several serious issues in SSMS with that. That’s why I am not currently planning to publish it.
Jakub
that’s awesome, I have been looking for that functionality for quite some time, and that is honestly my ideal implementation. If you still aren’t planning to release it for a while, what “quick find” apps are you currently using, i havent’ been able to find any so far.
I am now killed with other project but planning to involve this into SQL Treeo.
Hi Mark,Yes, I fully accept what you’re saniyg here, in a pro-actively managed environment it can be good to know all your databases will be created in a certain location, and if you have company build and configuration standards then yes I’d agree with you that its a setting you should consider setting away from the defaults. The problem I came across was with a server that had no DBA, no build standards and the person who configured SQL Server many years ago was long gone very different to the well managed environments we prefer. In those situations I’ll now check the default file location and that they exist before applying a service pack.