There are a couple issues that can occur within SQL that may cause some server-side performance, which can create performance issues within GlobalSearch.

Problem

SQL Server Eating Up All Server RAM

SQL will use as much RAM as it thinks it needs, regardless of the memory consumption of other applications on the server. This can lead to a SQL Server Instance causing a server to become unstable or have performance spikes. You can mitigate this issue by stipulating an upper threshold of memory usage for the SQL Server.

Solution

Limit SQL Server Usage

  1. Open SQL Server Management Studio (SSMS)
  2. Right click the database object in the object explorer and click "Properties"
  3. Select the "Memory" page and set "Maximum server memory (in MB):" to your maximum desired usage
  4. Hit "OK" and restart your SQL Server

Problem

SQL Databases are Constantly Opening and Closing, filling up Event Viewer with Notifications

Often times GlobalSearch databases are set to utilize "Autoclose" which constantly open and close with each connection. This can cause issues with performance both on the SQL side, and needlessly fill up your Event Viewer with verbose data, and in some cases, cause other system issues.

Solution

Disable Auto Close

  1. Open SQL Server Management Studio (SSMS)
  2. Expand "Databases" in Object Explorer
  3. For each of your production databases and GlobalSearch System databases, do the following:
    1. Right click the database and click "Properties"
    2. Open the "Options: page
    3. Under the "Other Options" Section locate "Auto Close" under the "Automatic" Section (you may have to scroll upwards to find this section)
    4. Set "Auto Close" to False
    5. Hit "OK"