Database Administrators Stack Exchange is a question and answer site for database professionals who wish to improve their database skills and learn from others in the community. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I'm a huge fan of a lot of the Redgate tools, however at my current workplace they are very paranoid over anything interacting with live servers (in particular affecting performance).

So my question is specifically on their SQL Search tool, what impact does it have on a server? I'm assuming that there will be:

  1. Initial indexing (what does it interact with, idea on impact on server, can it be customised to not index live servers)
  2. Subsequent connections/refreshes (how is it determining if there is a change to be re-indexed and what performance/load impact that will have on a server)?
share|improve this question

SQL Server Profiler is very useful when it comes to solving problems like this - use the ApplicationName filter to trace data specific to a particular application (i.e. SQL Search in this case), capture the data when it is used and then analyze executed queries and their performance.

share|improve this answer
up vote 5 down vote accepted

Answer received from Redgate support:

Following are answers to your questions:

  1. When you load a database in SQL Search, it indexes and stores the info on cache for giving search results. To not index specific servers, just do not select 'All database' nor pick the database you do not want to index in the database filter.

  2. Whenever you have mode modifications or want the index to be refreshed, manually refresh the index from the menu in SQL Search.

Hope that helps.

Thanks, Anuradha Deshpande

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.