Database Management
Health Score Calculations on Client vs. Health Score on Portal
The purpose of this how-to article is to explain why the health score may appear differently between the Client and the Portal.
First published date
6/2/2022 7:02 PM
Last published date
2/3/2023 9:23 PM
Overview
The default time range for the Health Score in Portal is based on the last 7 days, but the client defaults to the last 24 hours (with an additional smaller time sample available). So they would not match mostly due to differences in time scope. However, the Thick client includes all alerts in the health score (Like job failures, deadlocks, blocking, etc). However, the Portal only calculates based on Advisory Conditions. This can lead to different health scores between the Client and the Portal. (The scores in the screenshots below are examples)
Product section
SQL Sentry (SQLS)
Cause
N/A
Resolution
The solid explanation for any differences is the Portal only shows Advisory Conditions - where the Thick Client has both AC and Legacy, and this may cause different results between the two with the algorithm applied.