I like the search/filter text boxes that appear in some functional areas of the product.
One additional place I'd like to see it, for sure, is in the left-hand pane where I expand the collection of stored procs on the server, and am faced with a monstrously long scrolling job. Being able to whack a few keys into a text box in that pane to reduce the list of procs to only those containing the substring as I type -- it'd be a big help!
Shucks, it just doesn't work as nicely as the search in the query results pane -- which doesn't care what position in the string the search term is. The schema browser is looking for the beginning of the string. That's a pain when naming conventions park the term of interest in the middle of object names.
I actually can't use either of those methods. The first doesn't help with substrings amid the object names, and the second is not ad hoc enough.
Thanks, though...
Shucks, it just doesn't work as nicely as the search in the query results pane -- which doesn't care what position in the string the search term is. The schema browser is looking for the beginning of the string. That's a pain when naming conventions park the term of interest in the middle of object names.
I actually can't use either of those methods. The first doesn't help with substrings amid the object names, and the second is not ad hoc enough.
Thanks, though...
@scot: The schema browser is not looking only at the beginning of Object Names.
You can type *substring and ADS will locate the object in the Schema Tree. See attached screenshot in which I am searching for Log using *Log and it quickly positions on dbo.uspLogError. Can you try this and let me know if this works for you?
@scot: The schema browser is not looking only at the beginning of Object Names.
You can type *substring and ADS will locate the object in the Schema Tree. See attached screenshot in which I am searching for Log using *Log and it quickly positions on dbo.uspLogError. Can you try this and let me know if this works for you?
There's one BIG thing you could do to improve this. Well, a second smaller thing as well.
First, allow the search to penetrate subtrees that may happen to be closed. If I want to quickly get to all tables, views, functions and procs that include the substring *goal, I don't want to have to open each subtree first. That makes the ad hoc value of the search substantially less ad hocy. ;-)
This can be valuable when you want to find anything at all with a particular substring in its name, across all kinds of objects. In a given database, anyway.
The second thing would be to not have to wait to key arrow-down to see where the next hit is -- just highlight 'em all in yellow (unfolding the tree as necessary) at the outset, permitting scrolling to arbitrary locations in the results in the tree, rather than needing to arrow-down linearly from one result to the next.
Two cents.
There's one BIG thing you could do to improve this. Well, a second smaller thing as well.
First, allow the search to penetrate subtrees that may happen to be closed. If I want to quickly get to all tables, views, functions and procs that include the substring *goal, I don't want to have to open each subtree first. That makes the ad hoc value of the search substantially less ad hocy. ;-)
This can be valuable when you want to find anything at all with a particular substring in its name, across all kinds of objects. In a given database, anyway.
The second thing would be to not have to wait to key arrow-down to see where the next hit is -- just highlight 'em all in yellow (unfolding the tree as necessary) at the outset, permitting scrolling to arbitrary locations in the results in the tree, rather than needing to arrow-down linearly from one result to the next.
Two cents.
Issue #14319 |
Closed |
Fixed |
Resolved |
Completion |
No due date |
No fixed build |
No time estimate |