Comments
Sort by recent activity
It's been almost half a year - is there any progress on this issue? / comments
It's been almost half a year - is there any progress on this issue?
Hi Aaron,
yeah, that's what I thought [image]
Thanks for clarifying though.
BTW, this was your chance to come up with some awesome name like "Super Selection Function" or something... Missed that! :mrgreen: / comments
Hi Aaron,
yeah, that's what I thought
Thanks for clarifying though.
BTW, this was your chance to come up with some awesome name like "Super Selection Function" or something... Missed that! :mrgreen:
deathtospam wrote:
I also experience common crashes, albeit due to "Out of Memory" exceptions. At no point before I installed Red Gate did I ever get such errors. I'm running the SSMS tools against a server (not doing the work locally); my local machine has 8GB and utilization is never close to maxed when I get these errors.
In many cases, SQL Search is the only thing that I'm "running" in SSMS when the exception occurs -- it's not like it only happens when I run a world-ending query.
I think this could be the same issue that I experience (https://forums.red-gate.com/viewtopic.php?f=175&t=20747#p137922) when SQL Search defaults to "all databases" and starts indexing them. / comments
deathtospam wrote:
I also experience common crashes, albeit due to "Out of Memory" exceptions. At no point before I installed Red Gate did I ever get such errors. I'm running the SSMS tools ag...
csuire wrote:
SQLSearch2 sometimes detects the current database.
Othertimes it defaults to all databases.
For servers with LOTS of database, it can be annoying when it defaults to all databases.
The UI does not allow you to type a specific database name into the dropdown to aid in finding a specific database, which results in lots of scrolling.
When the SQL Search 2 database control has focus. Can you add support for typing the name of the database and have it narrow down the list as you type, and without using the mouse, select a specific database from the list.
Maybe also add an option to prevent SQL Search 2 from defaulting to All Databases. When the option it turned on, it would default to no database -- or be better at detecting the current database.
I agree with the OP that the behaviour of SQL Search to sometimes default to "all databases" is an issue.
I could live with the extra scrolling and having to deselect and select databases, but the real problem is that when all databases are selected, SQL Search starts to index all those databases. On a server with 300+ databases that takes a lot of RAM on the client and eventually leads to SQL Search crashing and me having to restart SSMS.
Could you please fix this? I think SQL Search should either never default to "all databases" or have an option to disable automatic indexing of selected databases.
Thanks. / comments
csuire wrote:
SQLSearch2 sometimes detects the current database.
Othertimes it defaults to all databases.
For servers with LOTS of database, it can be annoying when it defaults to all databases....