Skip to end of metadata
Go to start of metadata

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


SQL Server Eating Up All Server RAM

SQL will user 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.


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


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.


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"


After an Upgrade, System Performance is Much Slower

Some clients may notice some system slowness issues after an upgrade. It may be due to a SQL Upgrade Script not properly running at time of upgrade. This is typically due to an install with insufficient SQL Permissions. Luckily, running the upgrade scripts is easy and can be done within minutes.


Always back up your SQL Server before running any sort of script against a production database. Additionally, large databases may take some time to upgrade. To prevent deadlocks, it's advisable to run these scripts either after hours or off-peak hours.


Run Upgrade Scripts

  1. Open SQL Server Management Studio (SSMS)
  2. In your Server Getsmart directory, locate a Script called "SSMasterUpgrader.sql" and run this script in SSMS
  3. In your Server Getsmart directory, locate a Script called "UpgradeScript.sql"
  4. Do the following for all your production databases
    1. Load this script into SSMS but do not run it.
    2. Do a "Find and Replace" search for "DynamicSQLfjdksahfjilsda" and replace with your production Database name (you should find three instances of this)
    3. Once the Database name has been properly set, run the script
    4. Repeat as necessary for each database