133 results found
-
Search Stored Procedure by name shows the SQL Jobs and Steps that procedure is called from
When you search for a stored procedure, it shows its name and details.
It would be helpful to know which SQL Server Jobs and steps call/execute that stored procedure. That allows me to understand the importance and extent to which that stored procedure is used.
4 votes -
Add a script to Alter for Stored procedures found in SQL Search.
Add a option when you right click on the stored procedure you found to script it to an alter page similar to how you can do that if you find a nested SP in your code.
3 votes -
Would be nice if the database (and other) filter(s) would persist their value across restarts.
I work on a server with hundreds of databases, but only deal with one. It would be nice if I could persistently filter to just the one.
1 vote -
Indexing Control
It's linked to other questions/requests, but slightly different. I would personally rather that indexing results were persisted between sessions and then updated in the background. As things stand, I have to wait around 3 minutes every time I want to search for something, which disrupts the workflow. I would much rather put up with cached results that were displayed immediately, whilst being refined in the background.
You could also use some more advanced operators (eg '-' for exclusions etc)
1 vote -
Provide column options. For example, searching tables for a specific field like zip code - data type shows where joins could be an issue
Provide column options. For example, searching tables for a specific field like zip code - data type would show where joins could be an issue if some are Float and others are Varchar
1 vote -
Database Triggers
Database Triggers are missing in result set.
2 votes -
Use SSMS fonts and keyword colors in Object Preview
One thing I like about ApexSQL Search is that it uses my configured font styles and keyword colors from SSMS in the object preview/definition window. I would LOVE to see this implemented in the RedGate tool because it would make it easier to read the object code.
3 votes -
CREATE TABLE definition for tables in preview pane
As with other objects, I would like to see the CREATE TABLE definition in the preview pane when a table is selected in the search results.
This would give the same information to the user that the current table preview gives, with the added bonus of being able to copy and paste the results if we want to re-create the same table (say, under a different database or schema, or just with a different name), just as we can for views, SPs etc.
3 votes -
SSMS Integration
It would be nice to have SQL Search integrated in Object Explorer context menu. It will simplify first step in search.
1 vote -
enabled
When Object Types: Jobs can you add something in Matches on Enabled Job and Scheduled Job ?
1 vote -
Font Size setting for SQL Search results
Simply allow font size settings on SQL Search results ... OR ... Post where in Windows this default font might be found. Current results are so small as to be very difficult to use
5 votes -
Adjust the overall font size in the UI by percentage like in a browser.
Adjust the overall font size in the UI by percentage like in a browser.
1 vote -
Start search at button press
Search start - please make it at button press. The current "automatic" start might be annoying, especially when a very long search starts automatically after the input fileds are touched/leaved.
18 votes -
SSMS Schema Folders compatibility
This add-on moves schemas to a folder (e.g. Database -> Tables -> Schemas -> list of individual tables). Both add-ons dramatically increase's SSMS' usability. Search for obvious reasons. Schema Folders for easy keyboard jump to objects (e.g. typing tab to jump to "TableName" instead of dbo.tab). But the 2 don't work together. "Select object in Object Explorer" no longer works once I have Schema Folders installed. It often ends up somewhere in the sys folder, without actually jumping to the object.
Having both work would be gravy for my data warehouse (100s of tables/procs) means lots of scrolling otherwise.
Add-on…
15 votes -
Search option 'match whole words only' does not work as expected with database objects.
Allow me to explain by examples.
Example A:
I enter the search term 'test' (without the apostrophes) and I DO NOT check the 'match whole words only' option. I get the following hits:
- somethinginfronttest
- testsomethingbehind
- test
- [test]
- dbo.test
- dbo.[test]
So far so good, all hits are as expected.Example B:
I then enter the search term 'test' (without the apostrophes) and I CHECK the 'match whole words only' option. I get the following hits:
- testAnd that's it. I do not get the following hits:
- somethinginfronttest
- testsomethingbehind
- [test]
- dbo.test…4 votes -
Search within results
Search within results
5 votes -
Case Sensitive Searches
Would like to be able to enable case-sensitive searching. JSON field names in SQL are case sensitive.
example: JSON_VALUE(MyJsonColumn, '$.caseSensitiveFieldName')
Sometimes not everyone on the team is on the same page during development, and half the team uses "CaseSensitiveFieldName" and the other half uses "caseSensitiveFieldName". Eventually we realize the disconnect and have to go back and standardize things. So a case sensitive search would really help.
1 vote -
Save Search Results
Please provide an option to save the search results to a file. This is very helpful when there are a lot of objects that match the search criteria.
14 votes -
Add a way to stop automatically searching when I open SQL Search
It remembers the last search term, but not which databases I limited to the last time I searched. So everytime I open it, it tries to search multiple databases that I don't have permissions to. At least once a week I get asked by the DBA's what on earth I am doing.
23 votes -
FIX IT! Whole word with semicolon ending means NO HIT!
Search for a Procedure that has NO parameters, and the code-line ends with a semicolon - Search IS BLIND! What a lousy BUG!
4 votes
- Don't see your idea?