If the WhatsUp Health Threshold reports that the WhatsUp polling service SQL queries have exceeded the threshold number, there are several steps you can take to resolve the problem, dependent on the SQL database you are using.
If you are using the default SQL Express database included with WhatsUp Gold:
Note: SQL Server Express is limited to 1 GB of memory and 1 CPU.
If the WhatsUp database file becomes fragmented, this can decrease database performance. Before defragmenting, you need to stop the WhatsUp services and applications as well as the SQL Server services to allow defragmentation utilities to operate on SQL's database files.
If you have a hard drive on a separate disk from your operating system drive, you can improve file performance by relocating the WhatsUp database files to this separate hard drive.
Note: Moving files between different partitions on the same hard drive will not increase file system performance.
Because SQL Express does not benefit from memory improvements (beyond the 1GB limit), increasing file I/O performance provides a decrease in SQL statement execution time.
If you are using a non-default SQL configuration, such as SQL Standard installed on another computer:
The single biggest performance improvement available to any database application is additional memory.
Important: Be sure to consider the memory limitation of the edition of SQL you have installed as well as any limitations imposed by the operating system.
If the WhatsUp database is located in a SQL instance shared by other databases, WhatsUp has to compete with other applications for database resources. Consider moving WhatsUp Gold's databases to a dedicated SQL instance.
If SQL is installed on a remote computer, ensure that network traffic between the WhatsUp application and the SQL Server is optimized. This includes both packet loss and latency between the WhatsUp computer and the SQL Server.