Do not start indexing automatically but let user to start it.
Do not start indexing automatically but let user to start it.
Our two database servers contain many databases. When I switch from one to another, the index is automatically started with the database dropdown box selected all databases as default. It crashes my SSMS a few times or when it did not crash, I need to wait long time to wait it to finish the indexing.
George Sun
shared this idea
-
Marko T commented
This is a frustrating BUG. It seems to me that because SQL Search is a free tool, it does not get much attention from RedGate. It is a shame. This kind of software behaviour affects customer satisfaction. I am currently using thousands of euros worth of RedGate products.
-
SQL_Search_User
commented
Wow, this is still not done?
Oy.
-
Anonymous
commented
yup, this is frustrating. Also, the indexer does not nicely handle databases to which the logged in user cannot connect. It logs a traceback, but why? Easier to handle this error, issue a simple warning and carry on
-
Anonymous
commented
It starts caching all databases only if previously selected database is missing on a new server. Everything is OK if the database with the same name exists on both.
-
Anonymous
commented
Fix it please, really annoying issue
-
Raja S
commented
This is a problem especially with production servers, The SQL Search by default indexes all the database, raising DBA alerts, We might need options index only the database that we select
-
Krishna
commented
Or, provide a 'Stop' function that can stop a not required search operation.