SQL Nexus is a tool that helps you identify the root cause of SQL Server performance issues. It loads and analyzes performance data collected by SQL LogScout, SQLDiag or PSSDiag. It can dramatically reduce the amount of time you spend manually analyzing data.
MIT License
356
stars
101
forks
source link
Check for other "Best Practices" we might be able to point out with tbl_ServerProperties #144
Table tbl_ServerProperties has 'cpu_count' and 'number of visible schedulers'. If those aren't equal, point out SQL not using all procs.
'VISIBLEONLINE_SCHEDULER_COUNT' is also there. Maybe redundant?
In a few cases we have heard of servers that might need a patch to fix perf issues we'd never catch in SQL alone.
'registry SystemManufacturer'
'registry SystemProductName'
We might be able to have a warning for those machines found.
'resource governor enabled' (not sure what this checks ...and just because it is on doesnt mean there is any effect.)
'possibly running in virtual machine' (just good to know especially with perf issues)
'sqlserver_start_time' & 'machine start time' (server hasn't been restarted in a "long" time? but how much is a "long" time? not patched, etc)
Table tbl_ServerProperties has 'cpu_count' and 'number of visible schedulers'. If those aren't equal, point out SQL not using all procs.
'VISIBLEONLINE_SCHEDULER_COUNT' is also there. Maybe redundant?
In a few cases we have heard of servers that might need a patch to fix perf issues we'd never catch in SQL alone.
'registry SystemManufacturer' 'registry SystemProductName' We might be able to have a warning for those machines found.
'resource governor enabled' (not sure what this checks ...and just because it is on doesnt mean there is any effect.) 'possibly running in virtual machine' (just good to know especially with perf issues) 'sqlserver_start_time' & 'machine start time' (server hasn't been restarted in a "long" time? but how much is a "long" time? not patched, etc)