Ghost Solution Suite 3.x console is slow or unresponsive: Optimization and SQL settings

Products

• Ghost Solution Suite

Issue/Introduction

If the Ghost Solution Suite (GSS) Console is slow or unresponsive, several database configuration settings or query filters may be causing performance degradation.

Environment

Symantec Ghost Solution Suite (GSS) 3.x

Cause

 

• High execution times resulting from dynamic computer group filters using non-exact match operations (e.g., contains, starts with, ends with).

• Outdated SQL Server statistics or unoptimized database configuration options.

 

Resolution

 

1. Configure SQL Server Options (for Remote GSS Consoles): If using multiple GSS consoles with a remote SQL Express database, ensure the following database options are enabled:

   • READ Committed Snapshot

   • Allow Recursive Triggers

   Note: If using SQL Server 2014 Express (installed by GSS Installer RU8 and lower), install the additional SQL Server Management Studio component from the Microsoft Download Center.

2. Optimize Dynamic Computer Group Filters: Avoid using filters with contains, starts with, or ends with. Use the is exactly operation whenever possible.

   • Non-exact match example (contains): Filter: If Application Name contains "Notepad" Executed SQL Query:

     SQL

      

     SELECT computer_id FROM application WHERE name LIKE '%Notepad%'
     

     Execution time can take ~3 seconds.

   • Exact match example (is exactly): Filter: If Application Name equals "Notepad++" Executed SQL Query:

     SQL

      

     SELECT computer_id FROM application WHERE name = 'Notepad++'
     

     Execution time takes ~150 ms (up to 20 times faster).

   Impact: Environments with 500+ client nodes experience significant performance degradation when processing multiple LIKE query conditions.

3. Update SQL Statistics: Run the following stored procedure to update database statistics and index query plans:

   SQL

    

   EXEC sp_updatestats
   

   • Important: Perform a full SQL database backup prior to execution.

   • Updating statistics consumes system resources and should be run during scheduled maintenance windows (e.g., monthly). Refer to Microsoft SQL Server Documentation for further details.

4. Review Shared SQL Instance Best Practices: If using a shared SQL instance, consider using Microsoft best practices for maintaining and enhancing performance on SQL Server.