Let me configure the maximum number of results returned
I understand the reasoning behind limiting the search results to 150 results, but it would be useful to have the ability to change this as needed.
Anonymous
shared this idea
Thank you for this suggestion. the new v2 release of SQL Search now allows you to lift the per-database limit for each search.
The default limit is 500 results per database, However, it is also possible to configure this limit by following these steps:
On 64-bit systems, create the registry key
“HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Red Gate”
if it does not already exist and
“HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Red Gate\SQLSearch 2”
if it does not already exist.
Create the following DWORD (32-bit) value
“HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Red Gate\SQLSearch 2\ResultsLimit”
and set its data to what you wish the results limit to be (note that the registry editor works with Hexadecimal by default, so you may wish to change the base to Decimal when setting the value data).
On 32-bit systems, create the registry key
“HKEY_LOCAL_MACHINE\SOFTWARE\Red Gate”
if it does not already exist and
“HKEY_LOCAL_MACHINE\SOFTWARE\Red Gate\SQLSearch 2”
if it does not already exist.
Create the following DWORD (32-bit) value
“HKEY_LOCAL_MACHINE\SOFTWARE\Red Gate\SQLSearch 2\ResultsLimit”
and set its data to what you wish the results limit to be (note that the registry editor works with Hexadecimal by default, so you may wish to change the base to Decimal when setting the value data).
It should not require a restart of SSMS to take effect either, as this value is checked every time a search is triggered.
We will now close this suggestion so that votes are re-allocated.
Thanks
SQL Search Development Team
-
Daver
commented
I'm assuming this request is to allow people to get back to work faster. I've got a suggestion in that the results check if the search text matches the name of an object, should immediately return something while a background tasks continues the search the contents of other objects, such as stored procedures body. 80% of the time, I'm simply trying to find something via the name of object and it would be nice to be able to see that object quickly... yes, the other 20% of the time I'm searching everything to see if and where that keyword is being used. Another suggestion is to have a checkbox to say only search for objects names; no field names, no stored procedure content, etc.
-
@Vicar - thanks for your comment. I agree that the experience is poor here and it needs improving. We hope to have resource available in the latter half of this year so hopefully we can get this issue to the top of the backlog.
-
Vicar Hernandez
commented
This limit has caused me trouble. Not realizing the limit was there, I submitted a report indicating that some string was found 150 times in the database. I was able to survive the fiasco but it would be nice if it had either configurable options or some way to say "show next 150"...
I find this tool REALLY useful!!!
-
Armando
commented
many years have passed, and nothing was done by this one
but here is a workaround for a few more results
thanks to yar229
http://www.red-gate.com/messageboard/viewtopic.php?t=13690 -
Andy
commented
You don't have to have an options page, simple pagination would do (or a "show all" button)
-
om
commented
I have found that this limiting of results actually causes the results to be inaccurate. For example, searching for a column in views for a single database does not return expected views with that column since the results stop at 150. When I replaced the DLL with the 400 resultset, then some of the expected views started to be returned. This really needs to be configurable for those that have and use 10000's of views; otherwise, it is better not to use it. I do love this tool otherwise.
