Impact of Redgate SQL Search on Server

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:

• Initial indexing (what does it interact with, idea on impact on server, can it be customised to not index live servers)

• 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)?

Answer received from Redgate support:


Following are answers to your questions:



-
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.

-
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

StackExchange Database Administrators Q#1044, answer score: 7